View PC28F320_6743822.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

intel strataflash ? memory (j3) 256-mbit (x8/x16) datasheet product features capitalizing on intel?s 0.25 and 0.18 micron, two- bit-per-cell technology, the intel strataflash ? memory (j3) device provides 2x the bits in 1x the space, with new features for mainstream performance. offered in 256- mbit (32-mbyte), 128-mbit (16-mbyte), 64-mbit, and 32-mbit densities, the j3 device brings reliable, two-bit- per-cell storage technology to the flash market segment. be nefits include more density in less space, high-speed interface, lowest cost-per-bit nor device, support for code and data storage, and easy migration to future devices. using the same nor-based etox? technology as inte l?s one-bit-per-cell products, the j3 device takes advantage of over one billion units of flash manufacturing experience since 1987. as a result, j3 components are ideal for code and data appli cations where high density and low cost are required. examples include networking, telecommunications, digital set top boxes, audio recording, and digital imaging. by applying flashfile? memory family pinouts, j3 memory components allow easy design migrations from existing word-wide flashfile memory (28f160s3 and 28f320s3), and first generation intel strataflash ? memory (28f640j5 and 28f320j5) devices. j3 memory components deliver a new generation of forward-compatible software support. by using the common flash interface (cfi) and the scalable command se t (scs), customers can take advantage of density upgrades and optimized write capabilities of future intel strataflash ? memory devices. manufactured on intel ? 0.18 micron etox? vii (j3c) and 0.25 micron etox? vi (j3a) process technology, the j3 memory device provides the highest levels of quality and reliability. performance ? 110/115/120/150 ns initial access speed ? 125 ns initial access speed (256 mbit density only) ? 25 ns asynchronous page mode reads ? 30 ns asynchronous page mode reads (256mbit density only) ? 32-byte write buffer ?6.8 s per byte effective programming time software ? program and erase suspend support ? flash data integrator (fdi), common flash interface (cfi) compatible security ? 128-bit protection register ?64-bit unique device identifier ?64-bit user programmable otp cells ? absolute protection with v pen = gnd ? individual block locking ? block erase/program lockout during power transitions architecture ? multi-level cell technology: high density at low cost ? high-density symmetrical 128-kbyte blocks ?256 mbit (256 blocks) (0.18m only) ?128 mbit (128 blocks) ? 6 4 mbit (64 blocks) ?32 mbit (32 blocks) quality and reliability ?operating temperature: -40 c to +85 c ? 100k minimum erase cycles per block ? 0.18 m etox? vii process (j3c) ? 0.25 m etox? vi process (j3a) packaging and voltage ? 56-lead tsop package ? 64-ball intel ? easy bga package ? lead-free packages available ? 48-ball intel ? vf bga package (32 and 64 mbit) (x16 only) ?v cc = 2.7 v to 3.6 v ?v ccq = 2.7 v to 3.6 v order number: 290667-021 march 2005 notice: this document contains information on new prod ucts in production. the specifications are subject to change without notice. verify with your local intel sales office that you have the latest datasheet before finalizing a design.
2 datasheet information in this document is provided in connection with intel? products. no license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. except as provided in intel's terms and conditions of sale for such products, intel assumes no liability whatsoever, and intel disclaims any express or implied warranty, relating to sale and/or use of intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. intel products are not intended for use in medical, life saving, or life sustaining applications. intel may make changes to specifications and product descriptions at any time, without notice. designers must not rely on the absence or characteristics of any features or instructions marked ?reserved? or ?undefined.? int el reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. the 3 volt intel strataflash? memory may contain design defects or errors known as errata which may cause the product to deviat e from published specifications. current characterized errata are available on request. contact your local intel sales office or your distributor to obtain the latest specifications and before placing your product o rder. copies of documents which have an ordering number and are referenced in this document, or other intel literature may be obtaine d by calling 1-800- 548-4725 or by visiting intel's website at http://www.intel.com. copyright ? 2005, intel corporation. all rights reserved. intel and etox are trademarks or registered trademarks of intel corporation or its subsidiaries in the united states and other countries. *other names and brands may be claimed as the property of others.
datasheet 3 contents contents 1.0 introduction ............................................................................................................................... .....7 1.1 nomenclature ................................................................................................................ .......7 1.2 conventions................................................................................................................. .........7 2.0 functional overview .....................................................................................................................8 2.1 block diagram ............................................................................................................... .......9 2.2 memory map.................................................................................................................. .....10 3.0 package information ...................................................................................................................11 3.1 56-lead tsop package .....................................................................................................11 3.2 easy bga (j3) package .....................................................................................................12 3.3 vf-bga (j3) package ........................................................................................................1 3 4.0 ballout and signal descriptions ................................................................................................14 4.1 easy bga ballout (32/64/128/256 mbit) .............................................................................14 4.2 56-lead tsop (32/64/128/256 mbit)..................................................................................15 4.3 vf bga ballout (32 and 64 mbit) .......................................................................................15 4.4 signal descriptions ......................................................................................................... ....16 5.0 maximum ratings and operating conditions ...........................................................................18 5.1 absolute maximum ratings ................................................................................................18 5.2 operating conditions ........................................................................................................ ..18 6.0 electrical specifications .............................................................................................................19 6.1 dc current characteristics .................................................................................................1 9 6.2 dc voltage characteristics.................................................................................................2 0 7.0 ac characteristics ......................................................................................................................22 7.1 read operations............................................................................................................. ....22 7.2 write operations ............................................................................................................ .....26 7.3 block erase, program, and lock-bit configuration performance .......................................27 7.4 reset operation............................................................................................................. .....29 7.5 ac test conditions.......................................................................................................... ...29 7.6 capacitance................................................................................................................. .......30 8.0 power and reset specifications ................................................................................................31 8.1 power-up/down characteristics.........................................................................................31 8.2 power supply decoupling...................................................................................................31 8.3 reset characteristics....................................................................................................... ...31 9.0 bus operations ............................................................................................................................32 9.1 bus operations overview ...................................................................................................32 9.1.1 bus read operation ..............................................................................................33 9.1.2 bus write operation ..............................................................................................33 9.1.3 output disable .......................................................................................................33 9.1.4 standby..................................................................................................................3 4 9.1.5 reset/power-down ................................................................................................34
contents 4 datasheet 9.2 device commands ............................................................................................................. 35 10.0 read operations .......................................................................................................................... 37 10.1 read array................................................................................................................. ......... 37 10.1.1 asynchronous page mode read ........................................................................... 37 10.1.2 enhanced configuration register (ecr)............................................................... 38 10.2 read identifier codes ...................................................................................................... ... 39 10.2.1 read status register............................................................................................. 39 10.3 read query/cfi............................................................................................................. ..... 41 11.0 programming operations ........................................................................................................... 42 11.1 byte/word program .......................................................................................................... .. 42 11.2 write to buffer............................................................................................................ ......... 42 11.3 program suspend............................................................................................................ ... 43 11.4 program resume............................................................................................................. ... 43 12.0 erase operations ......................................................................................................................... 44 12.1 block erase................................................................................................................ ......... 44 12.2 block erase suspend ........................................................................................................ .44 12.3 erase resume ............................................................................................................... ..... 45 13.0 security modes ............................................................................................................................ 46 13.1 set block lock-bit......................................................................................................... ...... 46 13.2 clear block lock-bits...................................................................................................... .... 46 13.3 protection register program .............................................................................................. 47 13.3.1 reading the protection register............................................................................ 47 13.3.2 programming the protection register.................................................................... 47 13.3.3 locking the protection register............................................................................. 47 13.4 array protection ........................................................................................................... ....... 49 14.0 special modes .............................................................................................................................. 5 0 14.1 set read configuration register command ...................................................................... 50 14.2 status (sts) ............................................................................................................... ........ 50 appendix a common flash interface .................................................................................................52 appendix b flow charts ......................................................................................................................59 appendix c design considerations ...................................................................................................68 appendix d additional information ....................................................................................................70 appendix e ordering information .......................................................................................................71
datasheet 5 contents revision history date of revision version description 07/07/99 -001 original version 08/03/99 -002 a 0 ?a 2 indicated on block diagram 09/07/99 -003 changed minimum block erase time,i ol , i oh , page mode and byte mode currents. modified rp# on ac waveform for write operations 12/16/99 -004 changed block erase time and t avwh removed all references to 5 v i/o operation corrected ordering information , valid combinations entries changed min program time to 211 s added du to lead descriptions table changed chip scale package to ball grid array package changed default read mode to page mode removed erase queuing from figure 10, block erase flowchart 03/16/00 -005 added program max time added erase max time added max page mode read current moved tables to correspond with sections fixed typographical errors in ordering information and dc parameter table removed v ccq1 setting and changed v ccq2/3 to v ccq1/2 added recommended resister value for sts pin change operation temperature range removed note that rp# could go to 14 v removed v ol of 0.45 v; removed v oh of 2.4 v updated i ccr typ values added max lock-bit program and lock times added note on max measurements 06/26/00 -006 updated cover sheet statement of 700 million units to one billion corrected table 10 to show correct maximum program times corrected error in max block program time in section 6.7 corrected typical erase time in section 6.7 2/15/01 -007 updated cover page to reflect 100k minimum erase cycles updated cover page to reflect 110 ns 32m read speed removed set read configuration command from table 4 updated table 8 to reflect reserved bits are 1-7; not 2-7 updated table 16 bit 2 definition from r to pss changed v penlk max voltage from 0.8 v to 2.0 v, section 6.4, dc characteristics updated 32mbit read parameters r1, r2 and r3 to reflect 110ns, section 6.5, ac characteristics?read-only operations (1,2) updated write parameter w13 (t whrl ) from 90 ns to 500 ns, section 6.6, ac characteristics?write operations updated max. program suspend latency w16 (t whrh1 ) from 30 to 75 s, section 6.7, block erase, program, and lock-bit configuration performance (1,2,3) 04/13/01 -008 revised section 7.0, ordering information
contents 6 datasheet 07/27/01 -009 added figure 4, 3 volt intel strataflash ? memory vf bga package (32 mbit) added figure 5, 3 volt intel strataflash ? memory vf bga mechanical specifications updated operating temperature range to extended (section 6.1 and table 22) reduced t ehqz to 35 ns. reduced t wheh to 0 ns added parameter values for ?40 c operation to lock-bit and suspend latency updated v lko and v penlk to 2.2 v removed note #4, section 6.4 and section 6.6 minor text edits 10/31/01 -010 added notes under lead descriptions for vf bga package removed 3.0 v - 3.6 v vcc, and vccq columns under ac characteristics removed byte mode read current row un dc characteristics added ordering information for vf bga package minor text edits 03/21/02 -011 changed datasheet to reflect the best known methods updated max value for clear block lock-bits time minor text edits 12/12/02 -012 added nomenclature for j3c (0.18 m) devices. 01/24/03 -013 added 115 ns access speed 64 mb j3c device. added 120 ns access speed 128 mb j3c device. added ?te? package designator for j3c tsop package. 12/09/03 -014 revised asynchronous page read description. revised write-to-buffer flow chart. updated timing waveforms. added 256-mbit j3c pinout. 1/3/04 -015 added 256mbit device timings, device id, and cfi information. also corrected vlko specification. 1/23/04 -016 corrected memory block count from 257 to 255. 1/23/04 -016 memory block count fix. 5/19/04 -018 restructured the datasheet layout. 7/7/04 -019 added lead-free part numbers and 8-word page information. 11/23/04 -020 added note to dc voltage characteristics table; ?speed bin? to read operations table; corrected format for ac waveform for reset operation figure; corrected ?r? and ?8w? headings in enhanced configuration register table because they were transposed; added 802 and 803 to ordering information and corrected 56- lead tsop combination number. 3/24/05 -021 corrected ordering information. date of revision version description
256-mbit j3 (x8/x16) datasheet 7 1.0 introduction this document describes the intel strataflash ? memory (j3) device. it includes a description of device features, operations, and specifications. 1.1 nomenclature amin: amin = a0 for x8 amin = a1 for x16 amax: 32 mbit amax = a21 64 mbit amax = a22 128 mbit amax = a23 256 mbit amax = a24 block: a group of flash cells that share common erase circuitry and erase simultaneously clear: indicates a logic zero (0) cui: command user interface mlc: multi-level cell otp: one time programmable plr: protection lock register pr: protection register prd protection register data program: to write data to the flash array rfu: reserved for future use set: indicates a logic one (1) sr: status register srd: status register data vpen: refers to a signal or package connection name v pen : refers to timing or voltage levels wsm: write state machine ecr: extended configuration register xsr: extended status register 1.2 conventions 0x: hexadecimal prefix 0b: binary prefix k (noun): 1,000 m (noun): 1,000,000 nibble 4 bits byte: 8 bits word: 16 bits kword: 1,024 words kb: 1,024 bits kb: 1,024 bytes mb: 1,048,576 bits mb: 1,048,576 bytes brackets: square brackets ([]) will be used to designate group membership or to define a group of signals with similar function (i.e., a[21:1], sr[4,1] and d[15:0]).
256-mbit j3 (x8/x16) 8 datasheet 2.0 functional overview the intel strataflash ? memory family contains high-density memories organized as 32 mbytes or 16mwords (256-mbit, available on the 0.18m lithography process only), 16 mbytes or 8 mwords (128-mbit), 8 mbytes or 4 mwords (64-mbit), and 4 mbytes or 2 mwords (32-mbit). these devices can be accessed as 8- or 16-bit words. the 128-mbit device is organized as one-hundred- twenty-eight 128-kbyte (131,072 bytes) erase blocks . the 64-mbit device is organized as sixty- four 128-kbyte erase blocks while the 32-mbit devi ce contains thirty-two 128-kbyte erase blocks. a 128-bit protection register has multiple uses, including unique flash device identification. the device?s optimized architecture and interface dramatically increases read performance by supporting page-mode reads. this read mode is ideal for non-clock memory systems. a common flash interface (cfi) permits software algorithms to be used for entire families of devices. this allows device-independent, jedec id-independent, and forward- and backward- compatible software support for the specified flash device families. flash vendors can standardize their existing interfaces for long-term compatibility. scalable command set (scs) allows a single, simple software driver in all host systems to work with all scs-compliant flash memory devices, independent of system-level packaging (e.g., memory card, simm, or direct-to-board placement). additionally, scs provides the highest system/device data transfer rates and minimizes device and system-level implementation costs. a command user interface (cui) serves as the interface between the system processor and internal operation of the device. a valid command sequence written to the cui initiates device automation. an internal write state machine (wsm) automatically executes the algorithms and timings necessary for block erase, program, and lock-bit configuration operations. a block erase operation erases one of the device?s 128-kbyte blocks typically within one second? independent of other blocks. each block can be independently erased 100,000 times. block erase suspend mode allows system software to suspend block erase to read or program data from any other block. similarly, program suspend allows system software to suspend programming (byte/ word program and write-to-buffer operations) to read data or execute code from any other block that is not being suspended. each device incorporates a write buffer of 32 bytes (16 words) to allow optimum programming performance. by using the write buffer, data is programmed in buffer increments. this feature can improve system program performance more than 20 times over non-write buffer writes. blocks are selectively and individually lockable in-system.individual block locking uses block lock-bits to lock and unlock blocks. block lock-bits gate block erase and program operations. lock-bit configuration operations set and clear lock-bits (set block lock-bit and clear block lock-bits commands). the status register indicates when the wsm?s block erase, program, or lock-bit configuration operation is finished. the sts (status) output gives an additional indicator of wsm activity by providing both a hardware signal of status (versus software po lling) and status masking (interrupt masking for background block erase, for example). status indication using sts minimizes both cpu overhead and system power consumption. when configured in level mode (default mode), it acts as a ry/ by# signal. when low, sts indicates that the wsm is performing a block erase, program, or lock- bit configuration. sts-high indicates that the wsm is ready for a new command, block erase is
256-mbit j3 (x8/x16) datasheet 9 suspended (and programming is inactive), program is suspended, or the device is in reset/power- down mode. additionally, the configuration command allows the sts signal to be configured to pulse on completion of programming and/or block erases. three ce signals are used to enable and disable the device. a unique ce logic design (see table 13, ?chip enable truth table? on page 33 ) reduces decoder logic typically required for multi-chip designs. external logic is not required when designing a single chip, a dual chip, or a 4- chip miniature card or simm module. the byte# signal allows either x8 or x16 read/w rites to the device. byte#-low selects 8-bit mode; address a0 selects between the low byte and high byte. byte#-high enables 16-bit operation; address a1 becomes the lowest order address and address a0 is not used (don?t care). a device block diagram is shown in figure 4 on page 14. when the device is disabled (see table 13 on page 33 ), with cex at v ih and rp# at v ih , the standby mode is enabled. when rp# is at v il , a further power-down mode is enabled which minimizes power consumption and provides write protection during reset. a reset time (t phqv ) is required from rp# going high until data outputs are valid. likewise, the device has a wake time (t phwl ) from rp#-high until writes to the cui are recognized. with rp# at v il , the wsm is reset and the status register is cleared. 2.1 block diagram figure 1. 3 volt intel strataflash ? memory block diagram 32-mbit: thirty-two 64-mbit: sixty-four 128-mbit: one-hundred twenty-eight 128-kbyte blocks input buffer output latch/multiplexer y-gating program/erase voltage switch data comparator status register identifier register data register i/o logic address latch address counter x-decoder y-decoder input buffer output buffer gnd vcc vpen ce0 ce1 ce2 we# oe# rp# byte# command user interface a[max:min] d[15:0] vcc write buffer write state machine multiplexer query sts vccq ce logic a[2:0]
256-mbit j3 (x8/x16) 10 datasheet 2.2 memory map figure 2. intel strataflash ? memory (j3) memory map 64-kword block 64-kword block 64-kword block 64-kword block word wide (x16) mode 1fffff 1f0000 7fffff 7f0000 01ffff 010000 00ffff 000000 a[24-1]: 256 mbit a [23-1]: 128 mbit a [22-1]: 64 mbit a [21-1]: 32 mbit 128-kbyte block 128-kbyte block 128-kbyte block 128-kbyte block byte-wide (x8) mode 03fffff 03e0000 0ffffff 0fe0000 003ffff 0020000 001ffff 0000000 a[24-0]: 256 mbit a [23-0]:128 mbit a [22-0]: 64 mbit a [21-0]: 32 mbit 32-mbit 64-mbit 64-kword block 3fffff 3f0000 128-kbyte block 07fffff 07e0000 31 1 0 127 63 31 1 0 127 63 128-mbit 64-kword block 128-kbyte block ffffff ff0000 1ffffff 1fe0000 255 255 256-mbit
256-mbit j3 (x8/x16) datasheet 11 3.0 package information 3.1 56-lead tsop package figure 3. 56-lead tsop package drawing and specifications table 1. 56-lead tsop dimension table millimeters inches sym min nom max notes min nom max notes package height a 1.200 0.047 standoff a 1 0.050 0.002 package body thickness a 2 0.965 0.995 1.025 0.038 0.039 0.040 lead width b 0.100 0.150 0.200 0.004 0.006 0.008 lead thickness c 0.100 0.150 0.200 0.004 0.006 0.008 package body length d 1 18.200 18.400 18.600 4 0.717 0.724 0.732 4 package body width e 13.800 14.000 14.200 4 0.543 0.551 0.559 4 lead pitch e 0.500 0.0197 terminal dimension d 19.800 20.00 20.200 0.780 0.787 0.795 lead tip length l 0.500 0.600 0.700 0.020 0.024 0.028 lead count n 56 56 lead tip angle ? 0 3 5 0 3 5 seating plane coplanarity y 0.100 0.004 lead to package offset z 0.150 0.250 0.350 0.006 0.010 0.014 a 0 l detail a y d c z pin 1 e d 1 b detail b see detail a e see detail b a 1 seating plane a 2 see note 2 see notes 1 and 3
256-mbit j3 (x8/x16) 12 datasheet 3.2 easy bga (j3) package notes: 1. for daisy chain evaluation unit information refer to the intel flash memory packaging technology web page at; www.intel.com/design/packtech/index.htm 2. for packaging shipping media information see www.intel.com/design/packtech/index.htm figure 4. intel strataflash ? memory (j3) easy bga mechanical specifications table 2. easy bga package dimensions millimeters inches symbol min nom max notes min nom max package height a 1.200 0.0472 ball height a1 0.250 0.0098 package body thickness a2 0.780 0.0307 ball (lead) width b 0.330 0.430 0.530 0.0130 0.0169 0.0209 package body width (32 mb, 64 mb, 128 mb, 256 mb) d 9.900 10.000 10.100 1 0.3898 0.3937 0.3976 package body length (32 mb, 64 mb, 128 mb) e 12.900 13.000 13.100 1 0.5079 0.5118 0.5157 package body length (256 mb) e 14.900 15.000 15.100 1 0.5866 0.5906 0.5945 pitch [e] 1.000 0.0394 ball (lead) count n 64 64 seating plane coplanarity y 0.100 0.0039 corner to ball a1 distance along d (32/64/128/256 mb) s1 1.400 1.500 1.600 1 0.0551 0.0591 0.0630 corner to ball a1 distance along e (32/64/128 mb) s2 2.900 3.000 3.100 1 0.1142 0.1181 0.1220 corner to ball a1 distance along e (256 mb) s2 3.900 4.000 4.100 1 0.1535 0.1575 0.1614 e seating plane s1 s2 e top view - ball side down bottom view - ball side up y a a1 d ball a1 corner a2 note: drawing not to scale a b c d e f g h 8 7654321 8 7 6 5 4 3 2 1 a b c d e f g h b ball a1 corner
256-mbit j3 (x8/x16) datasheet 13 3.3 vf-bga (j3) package notes: 1. for daisy chain evaluation unit information refer to the intel flash memory packaging technology web page at; www.intel.com/design/packtech/index.htm 2. for packaging shipping media information refer to the intel flash memory packaging technology web page at; www.intel.com/design/packtech/index.htm figure 5. intel strataflash ? memory (j3) vf bga mechanical specifications e seating plane t op view - bum p s ide d own bottom view - ball side u p y a a1 d a2 ball a1 corner s1 s2 e b ball a1 corner a b c d e f 8 7 6 5 4 3 2 1 876 543 21 a b c d e f n ote: d rawing not to scale side view m illimeters inches symbol m in nom m ax n otes min nom max pa ckag e h eigh t a 1.000 0.0394 ba ll h e ig h t a 1 0.150 0.0059 pa ckage body t hickness a 2 0.665 0.0262 ball (lead ) w id th b 0.325 0.375 0.425 0.0128 0.0148 0.0167 d 7.186 7.286 7.386 1 0.2829 0.2868 0.2908 pa ckag e b o d y len g th e 10 .750 10.850 10 .950 1 0.4232 0.4272 0.4311 p it c h [ e ] 0 .7 5 0 0 .0 2 9 5 ba ll (le a d ) c o u n t n 48 48 se ating plan e c o p lan arity y 0.100 0.0039 co rn er to b a ll a 1 dis ta nc e a lo n g d s 1 0.918 1.018 1.118 1 0.0361 0.0401 0.0440 co rn er to b a ll a 1 dis ta nc e a lo n g e s 2 3.450 3.550 3.650 1 0.1358 0.1398 0.1437 n ote: (1) package dimensions are for reference only. t hese dimensions are estimates based on die size, and are sub j ect to chan g e. d im ensions table
256-mbit j3 (x8/x16) 14 datasheet 4.0 ballout and signal descriptions intel strataflash ? memory is available in three package types. each density of the j3c is supported on both 64-ball easy bga and 56-lead thin small outline package (tsop) packages. a 48-ball vf bga package is available on 32 and 64 mbit devices. figure 6 , figure 7 , and figure 8 show the pinouts. 4.1 easy bga ballout (32/64/128/256 mbit) notes: 1. address a22 is only valid on 64-mbit densities and above, otherwise, it is a no connect (nc). 2. address a23 is only valid on 128-mbit densities and above, otherwise, it is a no connect (nc). 3. address a24 is only valid on 256-mbit densities and above, otherwise, it is a no connect (nc). figure 6. intel strataflash ? memory easy bga ballout (32/64/128/256 mbit) easy bga top view- ball side down 1 8 234 5 67 ce2# rfu d13 vss d7 a24 256m vss h we# g byte # oe# f e sts d a4 a5 a11 r fu rp# a16 a17 rfu c a3 a7 a10 a1 5 a12 a20 a21 rfu b a2 vss a9 a1 4 ceo# a19 ce1# rfu a a1 a6 a8 a1 3 vpen a18 a22 vcc a23 128m a0 d2 d5 vccq d14 d6 d0 d10 d12 d11 rfu rfu d8 d1 d9 d4 d3 d15 rfu easy bga bottom view- ball side up 1 82 3 4 5 6 7 ce2# rfu d13 vss d7 a24 256m vss h we# g byte# oe# f e sts d a4 a5 a11 rfu rp# a16 a17 rfu c a3 a7 a10 a15 a 12 a20 a21 rfu b a2 vs s a9 a14 ceo# a19 ce1# rfu a a1 a6 a8 a13 vpen a18 a22 vcc a23 128m a0 d2 d5 vccq d14 d6 d0 d10 d12 d11 rfu rfu d8 d1 d9 d4 d3 d15 rfu vcc vcc
256-mbit j3 (x8/x16) datasheet 15 4.2 56-lead tsop (32/64/128/256 mbit) notes: 1. a22 exists on 64-, 128- and 256-mbit densities. on 32-mbit densities this signal is a no-connect (nc). 2. a23 exists on 128-mbit densities. on 32- and 64-mbit densities this signal is a no-connect (nc). 3. a24 exists on 256-mbit densities. on 32-, 64- and 128-mbit densities this signal is a no-connect (nc). 4. v cc = 5 v 10% for the 28f640j5/28f320j5. 4.3 vf bga ballout (32 and 64 mbit) notes: 1. ce# is equivalent to ce0, and ce1 and ce2 are internally grounded. 2. a22 exists on the 64 mb density only. on the 32-mbit density, this signal is a no-connect (nc). 3. sts not supported in this package. 4. x8 not supported in this package. figure 7. intel strataflash ? memory 56-lead tsop (32/64/128/256 mbit) highlights pinout changes 3 volt intel strataflash ? memory 56-lead tsop standard pinout 14 mm x 20 mm top view 1 3 4 2 5 7 8 6 9 11 12 10 13 15 16 14 17 19 20 18 21 23 24 22 25 27 28 26 56 54 53 55 52 50 49 51 48 46 45 47 44 42 41 43 40 38 37 39 36 34 33 35 32 30 29 31 oe# sts we# dq 15 dq 14 dq 6 dq 7 gnd dq 5 dq 12 dq 13 dq 4 gnd dq 11 v ccq dq 3 dq 2 v cc dq 10 dq 9 dq 8 dq 0 dq 1 a 0 ce 2 byte# a 21 a 20 ce 1 a 19 a 17 a 16 a 18 v cc a 14 a 13 a 15 a 12 v pen rp# ce 0 a 11 a 9 a 8 a 10 gnd a 6 a 5 a 7 a 4 a 2 a 1 a 3 a 22 (1) 32/64/128m 3 volt intel strataflash memory 32/64/128m 3 volt intel strataflash memory a 23 (2) a 24 (3) 28f320j5 nc oe# sts we# dq 15 dq 14 dq 6 dq 7 gnd dq 5 dq 12 dq 13 dq 4 gnd v ccq dq 11 dq 3 dq 10 v cc (4) dq 2 dq 9 dq 8 dq 0 dq 1 a 0 ce 2 byte# nc 28f320j5 a 11 a 9 a 8 a 10 gnd a 6 a 5 a 7 a 4 a 2 a 1 a 3 nc a 21 a 20 ce 1 a 19 a 17 a 16 a 18 a 14 a 13 a 15 a 12 v pen rp# ce 0 v cc (4) 28f160s3 a 20 ce 1 a 19 a 17 a 16 a 18 v cc nc nc a 14 a 13 a 15 a 12 ce 0 v pp rp# a 11 a 9 a 8 a 10 gnd a 6 a 5 a 7 a 4 a 2 a 1 a 3 28f160s3 oe# sts we# dq 15 dq 14 dq 6 dq 7 gnd wp# dq 5 dq 12 dq 13 dq 4 v cc gnd dq 11 dq 3 dq 2 v cc dq 10 dq 9 dq 8 dq 0 dq 1 a 0 byte# nc nc figure 8. intel strataflash ? memory vf bga ballout (32 and 64 mbit) vf b ga 6x8 top view - ball side down 2345678 1 a1 2 a9 vpen vcc a20 a8 a5 a11 w e# rp# a19 a1 8 a6 a3 a13 a1 0 a21 a7 a4 a2 d14d5d11 d2 d8 ce# d15 d6 d12 d3 d9 d0 vss d7 d 13 d 4 vcc d10 d 1 o e# a22 a1 a1 4 a15 a1 6 a1 7 vccq vss a b c d e f vf b ga 6x8 b ottom view - b all side up 2 3 4 5 6 7 81 a12 a9 vpen vcc a20 a8 a5 a1 1 we# rp# a1 9 a18 a6 a3 a1 3 a10 a21 a7 a4 a2 d 14 d 5 d11 d2 d 8 ce# d 15 d6 d12 d3 d9 d0 vss d7 d13 d4 vcc d10 d1 o e# a2 2 a1 a1 4 a1 5 a16 a17 vccq vss a b c d e f
256-mbit j3 (x8/x16) 16 datasheet 4.4 signal descriptions table 3 describes active signals used. table 3. signal descriptions (sheet 1 of 2) symbol type name and function a0 input byte-select address: selects between high and low byte when the device is in x8 mode. this address is latched during a x8 program cycle. not used in x16 mode (i.e., the a0 input buffer is turned off when byte# is high). a[max:1] input address inputs: inputs for addresses during read and program operations. addresses are internally latched during a program cycle. 32-mbit: a[21:0] 64-mbit: a[22:0] 128-mbit: a[23:0] 256-mbit: a[24:0] d[7:0] input/output low-byte data bus: inputs data during buffer writes and programming, and inputs commands during cui writes. outputs array, cfi, identifier, or status data in the appropriate read mode. data is internally latched during write operations. d[15:8] input/output high-byte data bus: inputs data during x16 buffer writes and programming operations. outputs array, cfi, or identifier data in the appropriate read mode; not used for status register reads. data is internally latched during write operations in x16 mode. d[15-8] float in x8 mode ce0, ce1, ce2 input chip enables: activates the device?s control logic, input buffers, decoders, and sense amplifiers. when the device is de-selected (see table 13 on page 33 ), power reduces to standby levels. all timing specifications are the same for these three signals. device selection occurs with the first edge of ce0, ce1, or ce2 that enables the device. device deselection occurs with the first edge of ce0, ce1, or ce2 that disables the device (see table 13 on page 33 ). rp# input reset/ power-down: rp#-low resets internal automation and puts the device in power- down mode. rp#-high enables normal operation. exit from reset sets the device to read array mode. when driven low, rp# inhibits write operations which provides data protection during power transitions. oe# input output enable: activates the device?s outputs through the data buffers during a read cycle. oe# is active low. we# input write enable: controls writes to the cui, the write buffer, and array blocks. we# is active low. addresses and data are latched on the rising edge of we#. sts open drain output status: indicates the status of the internal state machine. when configured in level mode (default), it acts as a ry/by# signal. when configured in one of its pulse modes, it can pulse to indicate program and/or erase completion. for alternate configurations of the status signal, see the configurations command. sts is to be tied to vccq with a pull-up resistor. byte# input byte enable: byte#-low places the device in x8 mode; data is input or output on d[7:0], while d[15:8] is placed in high-z. address a0 selects between the high and low byte. byte#- high places the device in x16 mode, and turns off the a0 input buffer. address a1 becomes the lowest-order address bit. vpen input erase / program / block lock enable: for erasing array blocks, programming data, or configuring lock-bits. with v pen v penlk , memory contents cannot be altered. vcc power core power supply: core (logic) source voltage. writes to the flash array are inhibited when v cc v lko . device operation at invalid vcc voltages should not be attempted. vccq power i/o power supply: i/o output-driver source voltage. this ball can be tied to v cc .
256-mbit j3 (x8/x16) datasheet 17 gnd supply ground: do not float any ground signals. nc ? no connect: lead is not internally connected; it may be driven or floated. rfu ? reserved for future use: balls designated as rfu are reserved by intel for future device functionality and enhancement . table 3. signal descriptions (sheet 2 of 2) symbol type name and function
256-mbit j3 (x8/x16) 18 datasheet 5.0 maximum ratings and operating conditions 5.1 absolute maximum ratings this datasheet contains information on new products in production. the specifications are subject to change without notice. verify with your local intel sales office that you have the latest datasheet before finalizing a design. absolute maximum ratings are shown in table 4 . warning: stressing the device beyond the ?absolute maximum ratings? may cause permanent damage . these are stress ratings only. operation beyond the ?operating conditions? is not recommended and extended exposure beyond the ?operating conditions? may affect device reliability. 5.2 operating conditions table 4. absolute maximum ratings parameter maximum rating temperature under bias extended ?40 c to +85 c storage temperature ?65 c to +125 c voltage on any signal ?2.0 v to +5.0 v (1) output short circuit current 100 ma (2) notes: 1. all specified voltages are with respect to gnd. minimum dc voltage is ?0.5 v on input/output signals and ?0.2 v on v cc and v pen signals. during transitions, this level may undershoot to ?2.0 v for periods <20 ns. maximum dc voltage on input/output signals, v cc , and v pen is v cc +0.5 v which, during transitions, may overshoot to v cc +2.0 v for periods <20 ns. 2. output shorted for no more than one second. no more than one output shorted at a time. table 5. temperature and v cc operating conditions symbol parameter min max unit test condition t a operating temperature ?40 +85 c ambient temperature v cc v cc1 supply voltage (2.7 v ? 3.6 v) 2.70 3.60 v ? v ccq v ccq supply voltage (2.7 v ? 3.6 v) 2.70 3.60 v ?
256-mbit j3 (x8/x16) datasheet 19 6.0 electrical specifications 6.1 dc current characteristics table 6. dc current characteristics (sheet 1 of 2) vccq 2.7 - 3.6v test conditions notes vcc 2.7 - 3.6v symbol parameter typ max unit i li input and v pen load current 1 a v cc = v cc max; v ccq = v ccq max v in = v ccq or gnd 1 i lo output leakage current 10 a v cc = v cc max; v ccq = v ccq max v in = v ccq or gnd 1 i ccs v cc standby current 50 120 a cmos inputs, v cc = v cc max, device is disabled (see table 13, ?chip enable truth table? on page 33 ), rp# = v ccq 0.2 v 1,2,3 0.71 2 ma ttl inputs, v cc = v cc max, device is disabled (see table 13 ), rp# = v ih i ccd v cc power-down current 50 120 a rp# = gnd 0.2 v, i out (sts) = 0 ma i ccr v cc page mode read current 4- word page 15 20 ma cmos inputs, v cc = v cc max, v ccq = v ccq max using standard 4 word page mode reads. device is enabled (see table 13 ) f = 5 mhz, i out = 0 ma 1,3 24 29 ma cmos inputs,v cc = v cc max, v ccq = v ccq max using standard 4 word page mode reads. device is enabled (see table 13 ) f = 33 mhz, i out = 0 ma 8- word page 10 15 ma ? cmos inputs, v cc = v cc max, v ccq = v ccq max using standard 8 word page mode reads. ? device is enabled (see table 13 ) f = 5 mhz, i out = 0 ma 30 54 ma ? cmos inputs,v cc = v cc max, v ccq = v ccq max using standard 8 word page mode reads. ? device is enabled (see table 13 ) f = 33 mhz, i out = 0 ma ? density: 128-, 64-, and 32- mbit 26 46 ma ? cmos inputs,v cc = v cc max, v ccq = v ccq max using standard 8 word page mode reads. ? device is enabled (see table 13 ) f = 33 mhz, i out = 0 ma ? density: 256mbit i ccw v cc program or set lock- bit current 35 60 ma cmos inputs, v pen = v cc 1,4 40 70 ma ttl inputs, v pen = v cc
256-mbit j3 (x8/x16) 20 datasheet 6.2 dc voltage characteristics i cce v cc block erase or clear block lock-bits current 35 70 ma cmos inputs, v pen = v cc 1,4 40 80 ma ttl inputs, v pen = v cc i ccws i cces v cc program suspend or block erase suspend current 10 ma device is enabled (see table 13 )1,5 notes: 1. all currents are in rms unless otherwise noted. these currents are valid for all product versions (packages and speeds). contact intel?s application support hotline or your local sales office for information about typical specifications. 2. includes sts. 3. cmos inputs are either v cc 0.2 v or gnd 0.2 v. ttl inputs are either v il or v ih . 4. sampled, not 100% tested. 5. i ccws and i cces are specified with the device selected. if the device is read or written while in erase suspend mode, the device?s current draw is i ccr and i ccws table 7. dc voltage characteristics symbol parameter min max unit test conditions notes v il input low voltage ?0.5 0.8 v 2, 6 v ih input high voltage 2.0 v ccq + 0.5 v2,6 v ol output low voltage 0.4 v v ccq = v ccq min i ol = 2 ma 1,2 0.2 v v ccq = v ccq min i ol = 100 a v oh output high voltage 0.85 v ccq v v ccq = v ccq min i oh = ?2.5 ma 1,2 v ccq ? 0.2 v v ccq = v ccq min i oh = ?100 a v penlk v pen lockout during program, erase and lock-bit operations 2.2 v 2,3,4,7 table 6. dc current characteristics (sheet 2 of 2) vccq 2.7 - 3.6v test conditions notes vcc 2.7 - 3.6v symbol parameter typ max unit
256-mbit j3 (x8/x16) datasheet 21 v penh v pen during block erase, program, or lock-bit operations 2.7 3.6 v 3,4 v lko v cc lockout voltage 2.0 v 5 notes: 1. includes sts. 2. sampled, not 100% tested. 3. block erases, programming, and lock-bit configurations are inhibited when v pen v penlk , and not guaranteed in the range between v penlk (max) and v penh (min), and above v penh (max). 4. typically, v pen is connected to v cc (2.7 v?3.6 v). 5. block erases, programming, and lock-bit configurations are inhibited when v cc < v lko , and not guaranteed in the range between v lko (min) and v cc (min), and above v cc (max). 6. includes all operational modes of the device including standby and power-up sequences. 7. vcc operating condition for standby has to meet typical operationg coditons. table 7. dc voltage characteristics symbol parameter min max unit test conditions notes
256-mbit j3 (x8/x16) 22 datasheet 7.0 ac characteristics 7.1 read operations table 8. read operations (sheet 1 of 2) asynchronous specifications (all units in ns unless otherwise noted) v cc = 2.7 v?3.6 v (3) v ccq = 2.7 v?3.6 v (3) notes speed bin -110 -115 -120 -125 -150 # sym parameter density min max min max min max min max min max r1 t avav read/write cycle time 32 mbit 110 1,2 64 mbit 115 120 1,2 128 mbit 120 150 1,2 256 mbit 125 1,2 r2 t avqv address to output delay 32 mbit 110 1,2 64 mbit 115 120 1,2 128 mbit 120 150 1,2 256 mbit 125 1,2 r3 t elqv ce x to output delay 32 mbit 110 1,2 64 mbit 115 120 1,2 128 mbit 120 150 1,2 256 mbit 125 1,2 r4 t glqv oe# to non- array output delay 50 50 50 50 50 1,2,4 r5 t phqv rp# high to output delay 32 mbit 150 1,2 64 mbit 180 180 1,2 128 mbit 210 210 1,2 256 mbit 210 r6 t elqx ce x to output in low z 0 0 0 0 0 1,2,5 r7 t glqx oe# to output in low z 0 0 0 0 0 1,2,5 r8 t ehqz ce x high to output in high z 35 35 35 35 35 1,2,5 r9 t ghqz oe# high to output in high z 15 15 15 15 15 1,2,5 r10 t oh output hold from address, ce x , or oe# change, whichever occurs first 0 0 0 0 0 1,2,5 r11 t elfl/ t elfh ce x low to byte# high or low 10 10 10 10 10 1,2,5
256-mbit j3 (x8/x16) datasheet 23 r12 t flqv/ t fhqv byte# to output delay 1000 1000 1000 1000 1000 1,2 r13 t flqz byte# to output in high z 1000 1000 1000 1000 1000 1,2,5 r14 t ehel cex high to cex low 0 0 0 0 0 1,2,5 r15 t apa page address access time 25 25 25 30 25 5, 6 r16 t glqv oe# to array output delay 25 25 25 25 25 4 notes: ce x low is defined as the first edge of ce0, ce1, or ce2 that enables the device. ce x high is defined at the first edge of ce0, ce1, or ce2 that disables the device (see table 13 ). 1. see ac input/output reference waveforms for the maximum allowable input slew rate. 2. oe# may be delayed up to t elqv -t glqv after the first edge of ce0, ce1, or ce2 that enables the device (see table 13 ) without impact on t elqv . 3. see figure 15, ?transient input/output reference waveform for vccq = 2.7 v?3.6 v? on page 29 and figure 16, ?transient equivalent testing load circuit? on page 30 for testing characteristics. 4. when reading the flash array a faster t glqv (r16) applies. non-array reads refer to status register reads, query reads, or device identifier reads. 5. sampled, not 100% tested. 6. for devices configured to standard word/byte read mode, r15 (t apa ) will equal r2 (t avqv ). figure 9. single word asynchronous read waveform table 8. read operations (sheet 2 of 2) asynchronous specifications (all units in ns unless otherwise noted) v cc = 2.7 v?3.6 v (3) v ccq = 2.7 v?3.6 v (3) notes speed bin -110 -115 -120 -125 -150 # sym parameter density min max min max min max min max min max r11 r5 r12 r13 r10 r4 r16 r7 r6 r9 r8 r3 r1 r2 r1 a ddress [a] cex [e] oe# [g] we# [w] data [d/q] byte#[f] rp# [p]
256-mbit j3 (x8/x16) 24 datasheet 0606_16 notes: 1. ce x low is defined as the last edge of ce0, ce1, or ce2 that enables the device. ce x high is defined at the first edge of ce0, ce1, or ce2 that disables the device (see table 13 ). 2. when reading the flash array a faster t glqv (r16) applies. for non-array reads, r4 applies (i.e.: status register reads, query reads, or device identifier reads). note: ce x low is defined as the last edge of ce0, ce1, or ce2 that enables the device. ce x high is defined at the first edge of ce0, ce1, or ce2 that disables the device (see table 13 ). figure 10. 4-word page mode read waveform 00 01 10 11 1 2 3 4 r10 r15 r10 r5 r9 r8 r7 r6 r4 r3 r1 r2 r1 a [max:3] [a] a[2:1] [a] cex [e] oe# [g] we# [w] d[15:0] [q] rp# [p]
256-mbit j3 (x8/x16) datasheet 25 notes: 1. ce x low is defined as the last edge of ce0, ce1, or ce2 that enables the device. ce x high is defined at the first edge of ce0, ce1, or ce2 that disables the device (see table 13 ). 2. in this diagram, byte# is asserted high. figure 11. 8-word asynchronous page mode read 1 2 6 8 r10 r15 r10 r5 r9 r8 r7 r6 r4 r3 r1 r2 r1 a [max:4] [a] a[3:1] [a] cex [e] oe# [g] we# [w] d[15:0] [q] rp# [p] byte#
256-mbit j3 (x8/x16) 26 datasheet 7.2 write operations table 9. write operations versions valid for all speeds unit notes # symbol parameter min max w1 t phwl (t phel ) rp# high recovery to we# (ce x ) going low 1 s 1,2,3 w2 t elwl (t wlel )ce x (we#) low to we# (ce x ) going low 0 ns 1,2,4 w3 t wp write pulse width 70 ns 1,2,4 w4 t dvwh (t dveh ) data setup to we# (ce x ) going high 50 ns 1,2,5 w5 t avwh (t aveh ) address setup to we# (ce x ) going high 55 ns 1,2,5 w6 t wheh (t ehwh )ce x (we#) hold from we# (ce x ) high 0 ns 1,2, w7 t whdx (t ehdx ) data hold from we# (ce x ) high 0 ns 1,2, w8 t whax (t ehax ) address hold from we# (ce x ) high 0 ns 1,2, w9 t wph write pulse width high 30 ns 1,2,6 w11 t vpwh (t vpeh )v pen setup to we# (ce x ) going high 0 ns 1,2,3 w12 t whgl (t ehgl ) write recovery before read 35 ns 1,2,7 w13 t whrl (t ehrl )we# (ce x ) high to sts going low 500 ns 1,2,8 w15 t qvvl v pen hold from valid srd, sts going high 0 ns 1,2,3,8,9 notes: ce x low is defined as the first edge of ce0, ce1, or ce2 that enables the device. ce x high is defined at the first edge of ce0, ce1, or ce2 that disables the device (see table 13 ). 1. read timing characteristics during block erase, program, and lock-bit configuration operations are the same as during read-only operations. refer to ac characteristics?read-only operations . 2. a write operation can be initiated and terminated with either ce x or we#. 3. sampled, not 100% tested. 4. write pulse width (t wp ) is defined from ce x or we# going low (whichever goes low last) to ce x or we# going high (whichever goes high first). hence, t wp = t wlwh = t eleh = t wleh = t elwh . 5. refer to table 14 for valid a in and d in for block erase, program, or lock-bit configuration. 6. write pulse width high (t wph ) is defined from ce x or we# going high (whichever goes high first) to ce x or we# going low (whichever goes low first). hence, t wph = t whwl = t ehel = t whel = t ehwl . 7. for array access, t avq v is required in addition to t whgl for any accesses after a write. 8. sts timings are based on sts configured in its ry/by# default mode. 9. v pen should be held at v penh until determination of block erase, program, or lock-bit configuration success (sr[1,3,4:5] = 0).
256-mbit j3 (x8/x16) datasheet 27 7.3 block erase, program, and lock-bit configuration performance table 10. configuration performance # sym parameter typ max (8) unit notes w16 write buffer byte program time (time to program 32 bytes/16 words) 218 654 s 1,2,3,4,5,6,7 w16 t whqv3 t ehqv3 byte program time (using word/byte program command) 210 630 s 1,2,3,4 block program time (using write to buffer command) 0.8 2.4 sec 1,2,3,4 w16 t whqv4 t ehqv4 block erase time 1.0 5.0 sec 1,2,3,4 w16 t whqv5 t ehqv5 set lock-bit time 64 75/85 s 1,2,3,4,9 w16 t whqv6 t ehqv6 clear block lock-bits time 0.5 0.70/1.4 sec 1,2,3,4,10 w16 t whrh1 t ehrh1 program suspend latency time to read 25 75/90 s 1,2,3,9 w16 t whrh t ehrh erase suspend latency time to read 26 35/40 s 1,2,3,9 notes: 1. typical values measured at t a = +25 c and nominal voltages. assumes corresponding lock-bits are not set. subject to change based on device characterization. 2. these performance numbers are valid for all speed versions. 3. sampled but not 100% tested. 4. excludes system-level overhead. 5. these values are valid when the buffer is full, and the start address is aligned on a 32-byte boundary. 6. effective per-byte program time (t whqv1 , t ehqv1 ) is 6.8 s/byte (typical). 7. effective per-word program time (t whqv2 , t ehqv2 ) is 13.6 s/word (typical). 8. max values are measured at worst case temperature and v cc corner after 100k cycles (except as noted). 9. max values are expressed at -25 c/-40 c. 10.max values are expressed at 25 c/-40 c.
256-mbit j3 (x8/x16) 28 datasheet figure 12. asynchronous write waveform figure 13. asynchronous write to read waveform d w11 w1 w1 3 w7 w4 w9 w9 w3 w3 w2 w6 w8 w5 address [a] cex (we# ) [e (w)] we# (cex) [w (e)] oe# [g] dat a [d/q] sts[r] rp# [p] vpen [v] d w1 1 w1 w7 w4 w12 w3 w3 w2 w6 w8 w5 address [a] ce# [e] we # [w] oe# [g] data [d/q] rst#/ rp# [p] vpen [v]
256-mbit j3 (x8/x16) datasheet 29 7.4 reset operation note: sts is shown in its default mode (ry/by#). 7.5 ac test conditions note: ac test inputs are driven at v ccq for a logic "1" and 0.0 v for a logic "0." input timing begins, and output timing ends, at v ccq /2 v (50% of v ccq ). input rise and fall times (10% to 90%) < 5 ns. figure 14. ac waveform for reset operation v ih v il p1 v il v ih p2 rp# (p) sts (r) table 11. reset specifications # sym parameter min max unit notes p1 t plph rp# pulse low time (if rp# is tied to v cc , this specification is not applicable) 35 s 1,2 p2 t phrh rp# high to reset during block erase, program, or lock-bit configuration 100 ns 1,3 notes: 1. these specifications are valid for all product versions (packages and speeds). 2. if rp# is asserted while a block erase, program, or lock-bit configuration operation is not executing then the minimum required rp# pulse low time is 100 ns. 3. a reset time, t phqv , is required from the latter of sts (in ry/by# mode) or rp# going high until outputs are valid. figure 15. transient input/output reference waveform for v ccq = 2.7 v?3.6 v outpu t test points input v ccq /2 v ccq 0.0 v ccq /2
256-mbit j3 (x8/x16) 30 datasheet note: c l includes jig capacitance. 7.6 capacitance t a = +25 c, f = 1 mhz figure 16. transient equivalent testing load circuit device under test ou t r l = 3.3 k ? 1n914 1.3v c l test configuration c l (pf) v ccq = v cc = 2.7 v ? 3.6 v 30 symbol parameter (1) type max unit condition c in input capacitance 6 8 pf v in = 0.0 v c out output capacitance 8 12 pf v out = 0.0 v notes: 1. sampled, not 100% tested.
256-mbit j3 (x8/x16) datasheet 31 8.0 power and reset specifications this section provides an overview of system level considerations for the intel strataflash ? memory family device. this section provides a brief description of power-up, power-down, decoupling and reset design considerations. 8.1 power-up/down characteristics in order to prevent any condition that may result in a spurious write or erase operation, it is recommended to power-up and power-down vcc and vccq together. it is also recommended to power-up vpen with or slightly after vcc. conversely, vpen must power down with or slightly before vcc. 8.2 power supply decoupling when the device is enabled, many internal conditions change. circuits are energized, charge pumps are switched on, and internal voltage nodes are ramped. all of this internal activities produce transient signals. the magnitude of the transient signals depends on the device and system loading. to minimize the effect of these transient signals, a 0.1 f ceramic capacitor is required across each vcc/vss and vccq signal . capacitors should be placed as close as possible to device connections. additionally, for every eight flash devices, a 4.7 f electrolytic capacitor should be placed between vcc and vss at the power supply connection. this 4.7 f capacitor should help overcome voltage slumps caused by pcb (printed circuit board) trace inductance. 8.3 reset characteristics by holding the flash device in reset during power-up and power-down transitions, invalid bus conditions may be masked. the flash device enters reset mode when rp# is driven low. in reset, internal flash circuitry is disabled and outputs are placed in a high-impedance state. after return from reset, a certain amount of time is required before the flash device is able to perform normal operations. after return from reset, the flash device defaults to asynchronous page mode. if rp# is driven low during a program or erase operation, the program or erase operation will be aborted and the memory contents at the aborted block or address are no longer valid. see figure 14, ?ac waveform for reset operation? on page 29 for detailed information regarding reset timings.
256-mbit j3 (x8/x16) 32 datasheet 9.0 bus operations this section provides an overview of device bus operations. the on-chip write state machine (wsm) manages all erase and program algorithms. the system cpu provides control of all in- system read, write, and erase operations of the device via the system bus. device commands are written to the cui to control all of the flash memory device?s operations. the cui does not occupy an addressable memory location; it?s the mechanism through which the flash device is controlled. 9.1 bus operations overview the local cpu reads and writes flash memory in-system. all bus cycles to or from the flash memory conform to standard microprocessor bus cycles. table 12. bus operations mode rp# ce[2:0] (1) oe# (2) we# (2) address vpen data (3) sts (default mode) notes read array v ih enabled v il v ih xx d out high z (7) 4,5,6 output disable v ih enabled v ih v ih x x high z x standby v ih disabled x x x x high z x reset/power-down mode v il x x x x x high z high z (7) read identifier codes v ih enabled v il v ih see table 17 x note 8 high z (7) read query v ih enabled v il v ih see table 10.3 x note 9 high z (7) read status (wsm off) v ih enabled v il v ih xx d out read status (wsm on) v ih enabled v il v ih xx d7 = d out d[15:8] = high z d[6:0] = high z write v ih enabled v ih v il xv penh d in x 6,10,11 notes: 1. see table 13 on page 33 for valid ce configurations. 2. oe# and we# should never be enabled simultaneously. 3. d refers to d[7:0] if byte# is low and d[15:0] if byte# is high. 4. refer to dc characteristics . when v pen v penlk , memory contents can be read, but not altered. 5. x can be v il or v ih for control and address signals, and v penlk or v penh for v pen . see dc characteristics for v penlk and v penh voltages. 6. in default mode, sts is v ol when the wsm is executing internal block erase, program, or lock-bit configuration algorithms. it is v oh when the wsm is not busy, in block erase suspend mode (with programming inactive), program suspend mode, or reset/power-down mode. 7. high z will be v oh with an external pull-up resistor. 8. see section 10.2, ?read identifier codes? on page 39 for read identifier code data. 9. see section 10.3, ?read query/cfi? on page 41 for read query data. 10.command writes involving block erase, program, or lock-bit configuration are reliably executed when v pen = v penh and v cc is within specification.
256-mbit j3 (x8/x16) datasheet 33 9.1.1 bus read operation to perform a bus read operation, cex (refer to table 13 on page 33 ) and oe# must be asserted. cex is the device-select control; when active, it enables the flash memory device. oe# is the data- output control; when active, the addressed flash memory data is driven onto the i/o bus. for all read states, we# and rp# must be de-asserted. see section 7.1, ?read operations? on page 22 . refer to section 10.0, ?read operations? on page 37 for details on reading from the flash array, and refer to section 14.0, ?special modes? on page 50 for details regarding all other available read states. 9.1.2 bus write operation writing commands to the command user interface enables various modes of operation, including the reading of array data, cfi data, identifier code s, inspection and clearing of the status register, and, when v pen = v penh , block erasure, program, and lock-bit configuration. the block erase command requires appropriate command data and an address within the block to be erased. the byte/word program command requires the command and address of the location to be written. set block lock-bit commands require the command and block within the device to be locked. the clear block lock-bits command requires the command and address within the device. the cui does not occupy an addressable memory location. it is written when the device is enabled and we# is active. the address and data needed to execute a command are latched on the rising edge of we# or the first edge of ce0, ce1, or ce2 that disables the device (see table 13 on page 33 ). standard microprocessor write timings are used. 9.1.3 output disable with cex asserted, and oe# at a logic-high level (v ih ), the device outputs are disabled. output signals d[15:0] are placed in a high-impedance state. table 13. chip enable truth table ce2 ce1 ce0 device v il v il v il enabled v il v il v ih disabled v il v ih v il disabled v il v ih v ih disabled v ih v il v il enabled v ih v il v ih enabled v ih v ih v il enabled v ih v ih v ih disabled note: for single-chip applications, ce2 and ce1 can be connected to v il .
256-mbit j3 (x8/x16) 34 datasheet 9.1.4 standby ce0, ce1, and ce2 can disable the device (see table 13 on page 33 ) and place it in standby mode. this manipulation of cex substantially reduces device power consumption. d[15:0] outputs are placed in a high-impedance state independent of oe#. if deselected during block erase, program, or lock-bit configuration, the wsm continues functioning, and consuming active power until the operation completes. 9.1.5 reset/power-down rp# at v il initiates the reset/power-down mode. in read modes, rp#-low deselects the memory, places output drivers in a high-impedance state, and turns off numerous internal circuits. rp# must be held low for a minimum of t plph . time t phqv is required after return from reset mode until initial memory access outputs are valid. after this wake- up interval, normal operation is restored. the cui is reset to read array mode and status register is set to 0x80. during block erase, program, or lock-bit configuration modes, rp#-low will abort the operation. in default mode, sts transitions low and remains low for a maximum time of t plph + t phrh until the reset operation is complete. memory contents being altered are no longer valid; the data may be partially corrupted after a program or partially alte red after an erase or lock-bit configuration. time t phwl is required after rp# goes to logic-high (v ih ) before another command can be written. as with any automated device, it is important to assert rp# during system reset. when the system comes out of reset, it expects to read from the flash memory. automated flash memories provide status information when accessed during block erase, program, or lock-bit configuration modes. if a cpu reset occurs with no flash memory reset, proper initialization may not occur because the flash memory may be providing status information instead of array data. intel strataflash ? memory family devices allow proper initialization following a system reset through the use of the rp# input. in this application, rp# is controlled by the same reset# signal that resets the system cpu.
256-mbit j3 (x8/x16) datasheet 35 9.2 device commands when the v pen voltage v penlk , only read operations from the status register, cfi, identifier codes, or blocks are enabled. placing v penh on v pen additionally enables block erase, program, and lock-bit configuration operations. device operations are selected by writing specific commands into the cui. table 14, ?command bus-cycle definitions? on page 35 defines these commands. table 14. command bus-cycle definitions (sheet 1 of 2) command scalable or basic command set (2) bus cycles req?d. first bus cycle second bus cycle notes oper (3) addr (4) data (5,6) oper (3) addr (4) data (5,6) read array scs/bcs 1 write x 0xff 1 read identifier codes scs/bcs 2 write x 0x90 read ia id 1,7 read query scs 2 write x 0x98 read qa qd 1 read status register scs/bcs 2 write x 0x70 read x srd 1,8 clear status register scs/bcs 1 write x 0x50 1 write to buffer scs/bcs > 2 write ba 0xe8 write ba n 1,9, 10, 11 word/byte program scs/bcs 2 write x 0x40 or 0x10 write pa pd 1,12,13 block erase scs/bcs 2 write ba 0x20 write ba 0xd0 1,11,12 block erase, program suspend scs/bcs 1 write x 0xb0 1,12,14 block erase, program resume scs/bcs 1 write x 0xd0 1,12 configuration scs 2 write x 0xb8 write x cc 1 set block lock-bit scs 2 write x 0x60 write ba 0x01 1
256-mbit j3 (x8/x16) 36 datasheet clear block lock-bits scs 2 write x 0x60 write x 0xd0 1,15 protection program 2 write x 0xc0 write pa pd 1 notes: 1. commands other than those shown above are reserved by intel for future device implementations and should not be used. 2. the basic command set (bcs) is the same as the 28f008sa command set or intel standard command set. the scalable command set (scs) is also referred to as the intel extended command set. 3. bus operations are defined in table 12 . 4. x = any valid address within the device. ba = address within the block. ia = identifier code address: see table 17 . qa = query database address. pa = address of memory location to be programmed. rcd = data to be written to the read configuration register. this data is presented to the device on a[16:1]; all other address inputs are ignored. 5. id = data read from identifier codes. qd = data read from query database. srd = data read from status register. see table 18 for a description of the status register bits. pd = data to be programmed at location pa. data is latched on the rising edge of we#. cc = configuration code. 6. the upper byte of the data bus (d[15:8]) during command writes is a ?don?t care? in x16 operation. 7. following the read identifier codes command, read operations access manufacturer, device and block lock codes. see section 10.2 for read identifier code data. 8. if the wsm is running, only d7 is valid; d[15:8] and d[6:0] float, which places them in a high-impedance state. 9. after the write to buffer command is issued check the xsr to make sure a buffer is available for writing. 10.the number of bytes/words to be written to the write buffer = n + 1, where n = byte/word count argument. count ranges on this device for byte mode are n = 00h to n = 1fh and for word mode are n = 0x00 to n = 0x0f. the third and consecutive bus cycles, as determined by n, are for writing data into the write buffer. the confirm command (0xd0) is expected after exactly n + 1 write cycles; any other command at that point in the sequence aborts the write to buffer operation. see figure 18, ?write to buffer flowchart? on page 59 for additional information 11.the write to buffer or erase operation does not begin until a confirm command (0xd0) is issued. 12.attempts to issue a block erase or program to a locked block. 13.either 0x40 or 0x10 are recognized by the wsm as the byte/word program setup. 14.program suspends can be issued after either the write-to-buffer or word/byte-program operation is initiated. 15.the clear block lock-bits operation simultaneously clears all block lock-bits. table 14. command bus-cycle definitions (sheet 2 of 2) command scalable or basic command set (2) bus cycles req?d. first bus cycle second bus cycle notes oper (3) addr (4) data (5,6) oper (3) addr (4) data (5,6)
256-mbit j3 (x8/x16) datasheet 37 10.0 read operations the device supports four types of read modes: read array, read identifier, read status, and cfi query. upon power-up or return from reset, the device defaults to read array mode. to change the device?s read mode, the appropriate read-mode command must be written to the device. (see section 9.2, ?device commands? on page 35 .) see section 14.0, ?special modes? on page 50 for details regarding read status, read id, and cfi query modes. upon initial device power-up or after exit from reset/power-down mode, the device automatically resets to read array mode. otherwise, write the appropriate read mode command (read array, read query, read identifier codes, or read status register) to the cui. six control signals dictate the data flow in and out of the component: ce0, ce1, ce2, oe#, we#, and rp#. the device must be enabled (see table 13, ?chip enable truth table? on page 33 ), and oe# must be driven active to obtain data at the outputs. ce0, ce1, and ce2 are the device selection controls and, when enabled (see table 13 ), select the memory device. oe# is the data output (d[15:0]) control and, when active, drives the selected memory data onto the i/o bus. we# must be at v ih . 10.1 read array upon initial device power-up and after exit from reset/power-down mode, the device defaults to read array mode. the device defaults to four-word asynchronous read page mode. the read array command also causes the device to enter read array mode. the device remains enabled for reads until another command is written. if the internal wsm has started a block erase, program, or lock- bit configuration, the device will not recognize the read array command until the wsm completes its operation unless the wsm is suspended via an erase or program suspend command. the read array command functions independently of the v pen voltage. 10.1.1 asynchronous page mode read there are two asynchronous page mode configurations that are available depending on the user?s system design requirements: ? four-word page mode: this is the default mode on power-up or reset. array data can be sensed up to four words (8 bytes) at a time. ? eight-word page mode: array data can be sensed up to eight words (16 bytes) at a time. this mode must be enabled on power-up or reset by using the command sequence found in table 14, ?command bus-cycle definitions? on page 35 . address bits a[3:1] determine which word is output during a read operation, and a[3:0] determine which byte is output for a x8 bus width. after the initial access delay, the first word out of the page buffer corresponds to the initial address. in four-word page mode, address bits a[2:1] determine which word is output from the page buffer for a x16 bus width, and a[2:0] determine which byte is output from the page buffer for a x8 bus width. subsequent reads from the device come fr om the page buffer. these reads are output on d[15:0] for a x16 bus width and d[7:0] for a x8 bus width after a minimum delay as long as a[2:0] (four-word page mode) or a[3:0] (eight-word page mode) are the only address bits that change. data can be read from the page buffer multiple times, and in any order. in four-word page mode, if address bits a[max:3] (a[max:4] for eight-word page mode) change at any time, or if ce# is toggled, the device will sense and load new data into the page buffer. asynchronous page mode is the default read mode on power-up or reset.
256-mbit j3 (x8/x16) 38 datasheet to perform a page mode read after any other operation, the read array command must be issued to read from the flash array. asynchronous page mode reads are permitted in all blocks and are used to access register information. during register access, only one word is loaded into the page buffer. 10.1.2 enhanced configuration register (ecr) the enhanced configuration register (ecr) is a volatile storage register that when addressed to by the set enhanced configuration register command, and can select between four-word page mode and eight-word page mode. the ecr is volatile; all bits will be reset to default values when rp# is deasserted or power is removed from the device. to modify ecr settings, use the set enhanced configuration register command. the set enhanced configuration register command is written along with the configuration register va lue, which is placed on the lower 16 bits of the address bus a[15:0]. this is followed by a second write that confirms the operation and again presents the enhanced configuration register data on the address bus. after executing this command, the device returns to read array mode. the ecr is shown in table 15, ?enhanced configuration register? on page 38 . note: for forward compatibility reasons, if the 8-word asynchronous page mode is to be used on j3c, a clear status register command must be issued after issuing the set enhanced configuration register command. see table 16, ?j3c asynchronous 8-word page mode command bus-cycle definition? on page 38 for further details. note: any reserved bits should be set to 0. note: x = any valid address within the device. ecd = enhanced configuration register data. table 15. enhanced configuration register res. reserved rr8wrrrrrrrrrrrrr ecr .15 ecr .14 ecr .13 ecr .12 ecr .11 ecr .10 ecr .9 ecr .8 ecr .7 ecr .6 ecr .5 ecr .4 ecr .3 ecr .2 ecr .1 ecr .0 bits description notes ecr[15:14] reserved reserved for future use. set to 0 until further notice. ecr[13] ? ?1? = 8word page mode ? ?0? = 4word page mode ecr[12:0] reserved reserved for future use. set to 0 until further notice. table 16. j3c asynchronous 8-word page mode command bus-cycle definition command bus cycles req?d. first bus cycle second bus cycle third bus cycle oper addr (1) data oper addr (1) data oper addr (1) data set enhanced configuration register (set ecr) 3 write ecd 0x60 write ecd 0x04 write x 0x50
256-mbit j3 (x8/x16) datasheet 39 10.2 read identifier codes the read identifier codes operation outputs the manufacturer code, device-code, and the block lock configuration codes for each block (see section 9.2, ?device commands? on page 35 for details on issuing the read device identifier command). page-mode reads are not supported in this read mode. to terminate the operation, write another valid command. like the read array command, the read identifier codes command functions independently of the v pen voltage. this command is valid only when the wsm is off or the device is suspended. following the read identifier codes command, the following information can be read. 10.2.1 read status register the status register may be read to determine when a block erase, program, or lock-bit configuration is complete and whether the operation completed successfully. it may be read only after the specified time w12 (see table 9, ?write operations? on page 26 ). after writing this command, all subsequent read operations output data from the status register until another valid command is written. page-mode reads are not supported in this read mode. the status register contents are latched on the falling edge of oe# or the first edge of ce0, ce1, or ce2 that enables the device (see table 13, ?chip enable truth table? on page 33 ). oe# must toggle to v ih or the device must be disabled before further reads to update the status register latch. the read status register command functions independently of the v pen voltage. during a program, block erase, set lock-bit, or clear lock-bit command sequence, only sr.7 is valid until the write state machine completes or suspends the operation. device i/o signals d[6:0] and d[15:8] are placed in a high-impedance state. when the operation completes or suspends (check sr.7), all contents of the status register are valid when read. table 17. read identifier codes code address (1) data manufacture code 00000 (00) 89 device code 32-mbit 00001 (00) 16 64-mbit 00001 (00) 17 128-mbit 00001 (00) 18 256-mbit 00001 (00) 1d block lock configuration x 0002 (2) ? block is unlocked d0 = 0 ? block is locked d0 = 1 ? reserved for future use d[7:1] notes: 1. a0 is not used in either x8 or x16 modes when obtaining the identifier codes. the lowest order address line is a1. data is always presented on the low byte in x16 mode (upper byte contains 00h). 2. x selects the specific block?s lock configuration code. 3. d[7:1] are invalid and should be ignored.
256-mbit j3 (x8/x16) 40 datasheet table 18. status register definitions wsms ess eclbs pslbs vpens pss dps r bit 7 bit 6 bit 5 bit 4 bit 3 bit2 bit 1 bit 0 high z when busy? status register bits notes no yes yes yes yes yes yes yes sr.7 = write state machine status 1 = ready 0 = busy sr.6 = erase suspend status 1 = block erase suspended 0 = block erase in progress/completed sr.5 = erase and clear lock-bitsstatus 1 = error in block erasure or clear lock-bits 0 = successful block erase or clear lock-bits sr.4 = program and set lock-bit status 1 = program error / error in setting lock-bit 0 = successful program/set block lock bit sr.3 = programming voltage status 1 = low programming voltage detected, operation aborted 0 = programming voltage ok sr.2 = program suspend status 1 = program suspended 0 = program in progress/completed sr.1 = device protect status 1 = block lock-bit detected, operation abort 0 = unlock sr0 = reserved for future enhancements check sts or sr.7 to determine block erase, program, or lock-bit configuration completion. sr[6:0] are not driven while sr.7 = ?0.? if both sr.5 and sr.4 are ?1?s after a block erase or lock-bit configuration attempt, an improper command sequence was entered. sr.3 does not provide a continuous programming voltage level indication. the wsm interrogates and indicates the programming voltage level only after block erase, program, set block lock-bit, or clear block lock-bits command sequences. sr.1 does not provide a continuous indication of block lock-bit values. the wsm interrogates the block lock-bits only after block erase, program, or lock-bit configuration command sequences. it informs the system, depending on the attempted operation, if the block lock-bit is set. read the block lock configuration codes using the read identifier codes command to determine block lock-bit status. sr0 is reserved for future use and should be masked when polling the status register. table 19. extended status register definitions wbs reserved bit 7 bits 6 -- 0 high z when busy? status register bits notes no yes xsr.7 = write buffer status 1 = write buffer available 0 = write buffer not available xsr.6?xsr0 = reserved for future enhancements after a buffer-write command, xsr.7 = 1 indicates that a write buffer is available. sr[6:0] are reserved for future use and should be masked when polling the status register.
256-mbit j3 (x8/x16) datasheet 41 10.3 read query/cfi the query register contains an assortment of flash product information such as block size, density, allowable command sets, electrical specifications and other product information. the data contained in this register conforms to the common flash interface (cfi) protocol. to obtain any information from the query register, execute the read query register command. see section 9.2, ?device commands? on page 35 for details on issuing the cfi query command. refer to appendix a, ?query structure overview? on page 53 for a detailed explanation of the cfi register. information contained in this register can onl y be accessed by executing a single-word read.
256-mbit j3 (x8/x16) 42 datasheet 11.0 programming operations the device supports two different programming methods: word programming, and write-buffer programming. successful programming requires the addressed block to be unlocked. an attempt to program a locked block will result in the operation aborting, and sr.1 and sr.4 being set, indicating a programming error. the following sections describe device programming in detail. 11.1 byte/word program byte/word program is executed by a two-cycle command sequence. byte/word program setup (standard 0x40 or alternate 0x10) is written followed by a second write that specifies the address and data (latched on the rising edge of we#). the wsm then takes over, controlling the program and program verify algorithms internally. after the program sequence is written, the device automatically outputs srd when read (see figure 20, ?byte/word program flowchart? on page 61 ). the cpu can detect the completion of the program event by analyzing the sts signal or sr.7. when program is complete, sr.4 should be checked. if a program error is detected, the status register should be cleared. the internal wsm verify only detects errors for ?1?s that do not successfully program to ?0?s. the cui remains in read status register mode until it receives another command. reliable byte/word programming can only occur when v cc and v pen are valid. if a byte/word program is attempted while v pen v penlk , sr.4 and sr.3 will be set. successful byte/word programs require that the corresponding block lock-bit be cleared. if a byte/word program is attempted when the corresponding block lock-bit is set, sr.1 and sr.4 will be set. 11.2 write to buffer to program the flash device, a write to buffer command sequence is initiated. a variable number of bytes, up to the buffer size, can be loaded into the buffer and written to the flash device. first, the write to buffer setup command is issued along with the block address (see figure 18, ?write to buffer flowchart? on page 59 ). at this point, the extended status register (xsr, see table 19 ) information is loaded and xsr.7 reverts to ?buffer available? status. if xsr.7 = 0, the write buffer is not available. to retry, continue monitoring xsr.7 by issuing the write to buffer setup command with the block address until xsr.7 = 1. when xsr.7 transitions to a ?1,? the buffer is ready for loading. next, a word/byte count is given to the part with the block address. on the next write, a device start address is given along with the write buffer data. subsequent writes provide additional device addresses and data, depending on the count. all subsequent addresses must lie within the start address plus the count. internally, this device programs many flash cells in parallel. because of this parallel programming, maximum programming performance and lower power are obtained by aligning the start address at the beginning of a write buffer boundary (i.e., a[4:0] of the start address = 0).
256-mbit j3 (x8/x16) datasheet 43 after the final buffer data is given, a write confirm command is issued. this initiates the wsm (write state machine) to begin copying the buffer data to the flash array. if a command other than write confirm is written to the device, an ?invalid command/sequence? error will be generated and sr.5 and sr.4 will be set. for additional buffer writes, issue another write to buffer setup command and check xsr.7. if an error occurs while writing, the device will stop writing, and sr.4 will be set to indicate a program failure. the internal wsm verify only detects errors for ?1?s that do not successfully program to ?0?s. if a program error is detected, the status register should be cleared. any time sr.4 and/or sr.5 is set (e.g., a media failure occurs during a program or an erase), the device will not accept any more write to buffer commands. additionally, if the user attempts to program past an erase block boundary with a write to buffer command, the device will abort the write to buffer operation. this will generate an ?invalid command/sequence? error and sr.5 and sr.4 will be set. reliable buffered writes can only occur when v pen = v penh . if a buffered write is attempted while v pen v penlk , sr.4 and sr.3 will be set. buffered write attempts with invalid v cc and v pen voltages produce spurious results and should not be attempted. finally, successful programming requires that the corresponding block lock-bit be reset. if a buffered write is attempted when the corresponding block lock-bit is set, sr.1 and sr.4 will be set. 11.3 program suspend the program suspend command allows program interruption to read data in other flash memory locations. once the programming process starts (either by initiating a write to buffer or byte/word program operation), writing the program suspend command requests that the wsm suspend the program sequence at a predetermined point in the algorithm. the device continues to output srd when read after the program suspend command is written. polling sr.7 can determine when the programming operation has been suspended. when sr.7 = 1, sr.2 should also be set, indicating that the device is in the program suspend mode. sts in level ry/by# mode will also transition to v oh . specification t whrh1 defines the program suspend latency. at this point, a read array command can be written to read data from locations other than that which is suspended. the only other valid commands while programming is suspended are read query, read status register, clear status register, configure, and program resume. after a program resume command is written, the wsm will continue the programming process. sr.2 and sr.7 will automatically clear and sts in ry/by# mode will return to v ol . after the program resume command is written, the device automatically outputs srd when read. v pen must remain at v penh and v cc must remain at valid v cc levels (the same v pen and v cc levels used for programming) while in program suspend mode. refer to figure 21, ?program suspend/resume flowchart? on page 62 . 11.4 program resume to resume (i.e., continue) a program suspend operation, execute the program resume command. the resume command can be written to any device address. when a program operation is nested within an erase suspend operation and the program suspend command is issued, the device will suspend the program operation. when the resume command is issued, the device will resume and complete the program operation. once the nested program operation is completed, an additional resume command is required to complete the block erase operation. the device supports a maximum suspend/resume of two nested routines. see figure 21, ?program suspend/resume flowchart? on page 62 ).
256-mbit j3 (x8/x16) 44 datasheet 12.0 erase operations flash erasing is performed on a block basis; therefore, only one block can be erased at a time. once a block is erased, all bits within that block will read as a logic level one. to determine the status of a block erase, poll the status register and analyze the bits. this following section describes block erase operations in detail. 12.1 block erase erase is executed one block at a time and initiated by a two-cycle command. a block erase setup is first written, followed by an block erase confirm. this command sequence requires an appropriate address within the block to be erased (erase changes all block data to ffh). block preconditioning, erase, and verify are handled internally by the wsm (invisible to the system). after the two-cycle block erase sequence is written, the device automatically outputs srd when read (see figure 22, ?block erase flowchart? on page 63 ). the cpu can detect block erase completion by analyzing the output of the sts signal or sr.7. toggle oe#, ce0, ce1, or ce2 to update the status register. when the block erase is complete, sr.5 should be checked. if a block erase error is detected, the status register should be cleared before system software attempts corrective actions. the cui remains in read status register mode until a new command is issued. this two-step command sequence of setup followed by execution ensures that block contents are not accidentally erased. an invalid block erase command sequence will result in both sr.4 and sr.5 being set. also, reliable block erasure can only occur when v cc is valid and v pen = v penh . if block erase is attempted while v pen v penlk , sr.3 and sr.5 will be set. successful block erase requires that the corresponding block lock-bit be cleared. if block erase is attempted when the corresponding block lock-bit is set, sr.1 and sr.5 will be set. 12.2 block erase suspend the block erase suspend command allows block-erase interruption to read or program data in another block of memory. once the block erase process starts, writing the block erase suspend command requests that the wsm suspend the block erase sequence at a predetermined point in the algorithm. the device outputs srd when read after the block erase suspend command is written. polling sr.7 then sr.6 can determine when the block erase operation has been suspended (both will be set). in default mode, sts will also transition to v oh . specification t whrh defines the block erase suspend latency. at this point, a read array command can be written to read data from blocks other than that which is suspended. a program command sequence can also be issued during erase suspend to program data in other blocks. during a program operation with block erase suspended, sr.7 will return to ?0? and sts output (in default mode) will transition to v ol . however, sr.6 will remain ?1? to indicate block erase suspend status. using the program suspend command, a program operation can also be suspended. resuming a suspended programming operation by issuing the program resume command allows continuing of the suspended programming operation. to resume the suspended erase, the user must wait for the programming operation to complete before issuing the block erase resume command.
256-mbit j3 (x8/x16) datasheet 45 the only other valid commands while block erase is suspended are read query, read status register, clear status register, configure, and block erase resume. after a block erase resume command is written to the flash memory, the wsm will continue the block erase process. sr.6 and sr.7 will automatically clear and sts (in default mode) will return to v ol . after the erase resume command is written, the device automatically outputs srd when read (see figure 23, ?block erase suspend/resume flowchart? on page 64 ). v pen must remain at v penh (the same v pen level used for block erase) while block erase is suspended. block erase cannot resume until program operations initiated during block erase suspend have completed. 12.3 erase resume to resume (i.e., continue) an erase suspend operation, execute the erase resume command. the resume command can be written to any device address. when a program operation is nested within an erase suspend operation and the program suspend command is issued, the device will suspend the program operation. when the resume command is issued, the device will resume the program operations first. once the nested program operation is completed, an additional resume command is required to complete the block erase operation. the device supports a maximum suspend/resume of two nested routines. see figure 22, ?block erase flowchart? on page 63 .
256-mbit j3 (x8/x16) 46 datasheet 13.0 security modes this device offers both hardware and software security features. block lock operations, prs, and vpen allow the user to implement various levels of data protection. the following section describes security features in detail. other security features are available that are not described in this datasheet. please contact your local intel field representative for more information. 13.1 set block lock-bit a flexible block locking scheme is enabled via block lock-bits. the block lock-bits gate program and erase operations. individual block lock-bits can be set using the set block lock-bit command. this command is invalid while the wsm is running or the device is suspended. set block lock-bit commands are executed by a two-cycle sequence. the set block setup along with appropriate block address is followed by either the set block lock-bit confirm (and an address within the block to be locked). the wsm then controls the set lock-bit algorithm. after the sequence is written, the device automatically outputs status register data when read (see figure 24 on page 65 ). the cpu can detect the completion of the set lock-bit event by analyzing the sts signal output or sr.7. when the set lock-bit operation is complete, sr.4 should be checked. if an error is detected, the status register should be cleared. the cui will remain in read status register mode until a new command is issued. this two-step sequence of setup followed by execution ensures that lock-bits are not accidentally set. an invalid set block lock-bit command will result in sr.4 and sr.5 being set. also, reliable operations occur only when v cc and v pen are valid. with v pen v penlk , lock-bit contents are protected against alteration. 13.2 clear block lock-bits all set block lock-bits are cleared in parallel via the clear block lock-bits command. block lock- bits can be cleared using only the clear block lock-bits command. this command is invalid while the wsm is running or the device is suspended. clear block lock-bits command is executed by a two-cycle sequence. a clear block lock-bits setup is first written. the device automatically outputs status register data when read (see figure 25 on page 66 ). the cpu can detect completion of the clear block lock-bits event by analyzing the sts signal output or sr.7. when the operation is complete, sr.5 should be checked. if a clear block lock-bit error is detected, the status register should be cleared. the cui will remain in read status register mode until another command is issued.
256-mbit j3 (x8/x16) datasheet 47 this two-step sequence of setup followed by execution ensures that block lock-bits are not accidentally cleared. an invalid clear block lock-bits command sequence will result in sr.4 and sr.5 being set. also, a reliable clear block lock-bits operation can only occur when v cc and v pen are valid. if a clear block lock-bits operation is attempted while v pen v penlk , sr.3 and sr.5 will be set. if a clear block lock-bits operation is aborted due to v pen or v cc transitioning out of valid range, block lock-bit values are left in an undetermined state. a repeat of clear block lock-bits is required to initialize block lock-bit contents to known values. 13.3 protection register program the intel strataflash ? memory (j3) includes a 128-bit protection register (pr) that can be used to increase the security of a system design. for example, the number contained in the pr can be used to ?mate? the flash component with other system components such as the cpu or asic, preventing device substitution. the 128-bits of the pr are divided into two 64-bit segments. one of the segments is programmed at the intel factory with a unique 64-bit number, which is unalterable. the other segment is left blank for customer designers to program as desired. once the customer segment is programmed, it can be locked to prevent further programming. 13.3.1 reading the protection register the protection register is read in the identification read mode. the device is switched to this mode by issuing the read identifier command (0x90). once in this mode, read cycles from addresses shown in table 8 or table 21 retrieve the specified information. to return to read array mode, write the read array command (0xff). 13.3.2 programming the protection register protection register bits are programmed using the two-cycle protection program command. the 64-bit number is programmed 16 bits at a time for word-wide configuration and eight bits at a time for byte-wide configuration. first write the protection program setup command, 0xc0. the next write to the device will latch in address and data and program the specified location. the allowable addresses are shown in table 8 or table 21 . see figure 26, ?protection register programming flowchart? on page 67 any attempt to address protection program commands outside the defined pr address space will result in a status register error (sr.4 will be set). attempting to program a locked pr segment will result in a status register error (sr.4 and sr.1 will be set). 13.3.3 locking the protection register the user-programmable segment of the protection register is lockable by programming bit 1 of the plr to 0. bit 0 of this location is programmed to 0 at the intel factory to protect the unique device number. bit 1 is set using the protection program command to program ?0xfffd? to the plr. after these bits have been programmed, no further changes can be made to the values stored in the protection register. protection program commands to a locked section will result in a status register error (sr.4 and sr.1 will be set). pr lockout state is not reversible.
256-mbit j3 (x8/x16) 48 datasheet note: a0 is not used in x16 mode when accessing the protection register map (see table 8 for x16 addressing). for x8 mode a0 is used (see table 21 for x8 addressing). figure 17. protection register memory map 0x88 0x85 64-bit segment (user-programmable) 0x84 0x81 0x80 lock register 0 64-bit segment (factory-programmed) 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 128-bit protection register 0 word address a[23:1]: 128 mbit a[21:1]: 32 mbit a[22:1]: 64 mbit a[24:1]: 256 mbit table 20. word-wide protection register addressing wordusea8a7a6a5a4a3a2a1 lockboth10000000 0factory10000001 1factory10000010 2factory10000011 3factory10000100 4user10000101 5user10000110 6user10000111 7user10001000 table 21. byte-wide protection register addressing (sheet 1 of 2) byteusea8a7a6a5a4a3a2a1a0 lockboth100000000 lockboth100000001 0factory100000010 1factory100000011 2factory100000100 3factory100000101 4factory100000110 5factory100000111
256-mbit j3 (x8/x16) datasheet 49 13.4 array protection the v pen signal is a hardware mechanism to prohibit array alteration. when the v pen voltage is below the v penlk voltage, array contents cannot be altered. to ensure a proper erase or program operation, v pen must be set to a valid voltage level. to determine the status of an erase or program operation, poll the status register and analyze the bits. 6factory100001000 7factory100001001 8user100001010 9user100001011 auser100001100 buser100001101 cuser100001110 duser100001111 euser100010000 fuser100010001 note: all address lines not specified in the above table must be 0 when accessing the protection register, i.e.g., a[max:9] = 0. table 21. byte-wide protection register addressing (sheet 2 of 2)
256-mbit j3 (x8/x16) 50 datasheet 14.0 special modes this section describes how to read the status, id, and cfi registers. this section also details how to configure the sts signal. 14.1 set read configuration register command this command is no longer supported on j3a or j3c. the j3a device will ignore this command, while the j3c device will result in an invalid command sequence (sr.4 and sr.5 =1). 14.2 status (sts) the status (sts) signal can be configured to different states using the configuration command. once the sts signal has been configured, it remains in that configuration until another configuration command is issued or rp# is asserted low. initially, the sts signal defaults to ry/ by# operation where ry/by# low indicates that the wsm is busy. ry/by# high indicates that the state machine is ready for a new operation or suspended. table 22, ?sts configuration coding definitions? on page 50 displays the possible sts configurations. to reconfigure the status (sts) signal to ot her modes, the configuration command is given followed by the desired configuration code. the thre e alternate configurations are all pulse mode for use as a system interrupt as described below. for these configurations, bit 0 controls erase complete interrupt pulse, and bit 1 controls program complete interrupt pulse. supplying the 0x00 configuration code with the configuration command resets the sts signal to the default ry/by# level mode. the possible configurations and their usage are described in table 22, ?sts configuration coding definitions? on page 50 . the configuration command may only be given when the device is not busy or suspended. check sr.7 for device status. an invalid configuration code will result in both sr.4 and sr.5 being set. when configured in one of the pulse modes, the sts signal pulses low with a typical pulse width of 250 ns. table 22. sts configuration coding definitions d7 d6 d5 d4 d3 d2 d1 d0 reserved pulse on program complete (1) pulse on erase complete (1) d[1:0] = sts configuration codes notes 00 = default, level mode; device ready indication used to control hold to a memory controller to prevent accessing a flash memory subsystem while any flash device's wsm is busy. 01 = pulse on erase complete used to generate a system interr upt pulse when any flash device in an array has completed a block erase. helpful for reformatting blocks after file system free space reclamation or ?cleanup.?
256-mbit j3 (x8/x16) datasheet 51 10 = pulse on program complete used to generate a system interrupt pulse when any flash device in an array has completed a program operation. provides highest performance for servicing continuous buffer write operations. 11 = pulse on erase or program complete used to generate system interrupts to trigger servicing of flash arrays when either erase or program operations are completed, when a common interrupt service routine is desired. notes: 1. when configured in one of the pulse modes, sts pulses low with a typical pulse width of 250 ns. 2. an invalid configuration code will result in both sr.4 and sr.5 being set. table 22. sts configuration coding definitions d7 d6 d5 d4 d3 d2 d1 d0 reserved pulse on program complete (1) pulse on erase complete (1) d[1:0] = sts configuration codes notes
256-mbit j3 (x8/x16) 52 datasheet appendix a common flash interface the common flash interface (cfi) specification outlines device and host system software interrogation handshake which allows specific vendor-specified software algorithms to be used for entire families of devices. this allows device independent, jedec id-independent, and forward- and backward-compatible software support for the specified flash device families. it allows flash vendors to standardize their existing interfaces for long-term compatibility. this appendix defines the data structure or ?database? returned by the common flash interface (cfi) query command. system software should parse this structure to gain critical information such as block size, density, x8/x16, and electrical specifications. once this information has been obtained, the software will know which command sets to use to enable flash writes, block erases, and otherwise control the flash component. the query command is part of an overall specification for multiple command set and control interface descriptions called common flash interface, or cfi. a.1 query structure output the query ?database? allows system software to gain information for controlling the flash component. this section describes the device?s cfi-compliant interface that allows the host system to access query data. query data are always presented on the lowest-order data outputs (d[7:0]) only. the numerical offset value is the address relative to the maximum bus width supported by the device. on this family of devices, the query table device starting address is a 10h, which is a word address for x16 devices. for a word-wide (x16) device, the first two bytes of the query structure, ?q? and ?r? in ascii, appear on the low byte at word addresses 10h and 11h. this cfi-compliant device outputs 00h data on upper bytes. thus, the device outputs ascii ?q? in the low byte (d[7:0]) and 0x00 (00h) in the high byte (d[15:8]). at query addresses containing two or more bytes of information, the least significant data byte is presented at the lower address, and the most signif icant data byte is presented at the higher address. in all of the following tables, addresses and data are represented in hexadecimal notation, so the ?h? suffix has been dropped. in addition, since the upper byte of word-wide devices is always ?00h,? the leading ?00? has been dropped from the table notation and only the lower byte value is shown. any x16 device outputs can be assumed to have 00h on the upper byte in this mode.
256-mbit j3 (x8/x16) datasheet 53 a.2 query structure overview the query command causes the flash component to display the common flash interface (cfi) query structure or ?database.? the structure sub-sections and address locations are summarized below. see ap-646 common flash interface (cfi) and command sets (order number 292204) for a full description of cfi commands. the following sections describe the query structure sub-sections in detail. table 23. summary of query structure output as a function of device and mode device type/ mode query start location in maximum device bus width addresses query data with maximum device bus width addressing query data with byte addressing hex offset hex code ascii value hex offset hex code ascii value x16 device 10h 10: 0051 ?q? 20: 51 ?q? x16 mode 11: 0052 ?r? 21: 00 ?null? 12: 0059 ?y? 22: 52 ?r? x16 device 20: 51 ?q? x8 mode n/a (1) n/a (1) 21: 51 ?q? 22: 52 ?r? note: 1. the system must drive the lowest order addresses to access all the device's array data when the device is configured in x8 mode. therefore, word addressing, where these lower addresses are not toggled by the system, is "not applicable" for x8-configured devices. table 24. example of query structure output of a x16- and x8-capable device word addressing byte addressing offset hex code value offset hex code value a 15 ?a 0 d15?d 0 a 7 ?a 0 d 7 ?d 0 0010h 0051 ?q? 20h 51 ?q? 0011h 0052 ?r? 21h 51 ?q? 0012h 0059 ?y? 22h 52 ?r? 0013h p_id lo prvendor 23h 52 ?r? 0014h p_id hi id # 24h 59 ?y? 0015h p lo prvendor 25h 59 ?y? 0016h p hi tbladr 26h p_id lo prvendor 0017h a_id lo altvendor 27h p_id lo id # 0018h a_id hi id # 28h p_id hi id # ... ... ... ... ... ...
256-mbit j3 (x8/x16) 54 datasheet a.3 block status register the block status register indicates whether an erase operation completed successfully or whether a given block is locked or can be accessed for flash program/erase operations. a.4 cfi query identification string the cfi query identification string provides verification that the component supports the common flash interface specification. it also indicates the specification version and supported vendor-specified command set(s). table 25. query structure offset sub-section name description notes 00h manufacturer code 1 01h device code 1 (ba+2)h (2) block status register block-specific information 1,2 04-0fh reserved reserved for vendor-specific information 1 10h cfi query identification string reserved for vendor-specific information 1 1bh system interface information command set id and vendor data offset 1 27h device geometry definition flash device layout 1 p (3) primary intel-specific extended query table vendor-defined additional information specific to the primary vendor algorithm 1,3 notes: 1. refer to the query structure output section and offset 28h for the detailed definition of offset address as a function of device bus width and mode. 2. ba = block address beginning location (i.e., 02000h is block 2?s beginning location when the block size is 128 kbyte). 3. offset 15 defines ?p? which points to the primary intel-specific extended query table. table 26. block status register offset length description address value (ba+2)h (1) 1 block lock status register ba+2: --00 or --01 bsr.0 block lock status 0 = unlocked 1 = locked ba+2: (bit 0): 0 or 1 bsr 1?7: reserved for future use ba+2: (bit 1?7): 0 note: 1. ba = the beginning location of a block address (i.e., 008000h is block 1?s (64-kb block) beginning location in word mode). table 27. cfi identification (sheet 1 of 2) offset length description add. hex code value 10h 3 query-unique ascii string ?qry? 10 --51 ?q? 11: --52 ?r? 12: --59 ?y? 13h 2 primary vendor command set and control interface id code. 13: --01 16-bit id code for vendor-specified algorithms 14: --00 15h 2 extended query table primary algorithm address 15: --31 16: --00 17h 2 alternate vendor command set and control interface id code. 17: --00
256-mbit j3 (x8/x16) datasheet 55 a.5 system interface information the following device information can optimize system interface software. a.6 device geometry definition this field provides critical details of the flash device geometry. 0000h means no second vendor-specified algorithm exists 18: --00 19h 2 secondary algorithm extended query table address. 19: --00 0000h means none exists 1a: --00 table 27. cfi identification (sheet 2 of 2) offset length description add. hex code value table 28. system interface information offset length description add. hex code value 1bh 1 v cc logic supply minimum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 bcd volts 1b: --27 2.7 v 1ch 1 v cc logic supply maximum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 bcd volts 1c: --36 3.6 v 1dh 1 v pp [programming] supply minimum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 hex volts 1d: --00 0.0 v 1eh 1 v pp [programming] supply maximum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 hex volts 1e: --00 0.0 v 1fh 1 ?n? such that typical single word program time-out = 2 n s 1f: --08 256 s 20h 1 ?n? such that typical max. buffer write time-out = 2 n s 20: --08 256 s 21h 1 ?n? such that typical block erase time-out = 2 n ms 21: --0a 1 s 22h 1 ?n? such that typical full chip erase time-out = 2 n ms 22: --00 na 23h 1 ?n? such that maximum word program time-out = 2 n times typical 23: --04 2 ms 24h 1 ?n? such that maximum buffer write time-out = 2 n times typical 24: --04 2 ms 25h 1 ?n? such that maximum block erase time-out = 2 n times typical 25: --04 16 s 26h 1 ?n? such that maximum chip erase time-out = 2 n times typical 26: --00 na table 29. device geometry definition (sheet 1 of 2) offset length description code see table below 27h 1 ?n? such that device size = 2 n in number of bytes 27: 28h 2 flash device interface: x8 async x16 async x8/x16 async 28: --02 x8/ x16 28:00,29:00 28:01,29:00 28:02,29:00 29: --00 2ah 2 ?n? such that maximum number of bytes in write buffer = 2 n 2a: --05 32 2b: --00
256-mbit j3 (x8/x16) 56 datasheet device geometry definition a.7 primary-vendor specific extended query table certain flash features and commands are optional. the primary vendor-specific extended query table specifies this and other similar information. 2ch 1 number of erase block regions within device: 1. x = 0 means no erase blocking; the device erases in ?bulk? 2. x specifies the number of device or partition regions with one or more contiguous same-size erase blocks 3. symmetrically blocked partitions have one blocking region 4. partition size = (total blocks) x (individual block size) 2c: --01 1 2dh 4 erase block region 1 information 2d: bits 0?15 = y, y+1 = number of identical-size erase blocks 2e: bits 16?31 = z, region erase block(s) size are z x 256 bytes 2f: 30: table 29. device geometry definition (sheet 2 of 2) offset length description code see table below address 32 mbit 64 mbit 128 mbit 256mbit 27: --16 --17 --18 --19 28: --02 --02 --02 --02 29: --00 --00 --00 -00 2a: --05 --05 --05 -05 2b: --00 --00 --00 -00 2c: --01 --01 --01 -01 2d: --1f --3f --7f -ff 2e: --00 --00 --00 --00 2f: --00 --00 --00 --00 30: --02 --02 --02 --02 table 30. primary vendor-specific extended query (sheet 1 of 2) offset (1) p = 31h length description (optional flash features and commands) add. hex code value (p+0)h 3 primary extended query table 31: --50 ?p? (p+1)h unique ascii string ?pri? 32: --52 ?r? (p+2)h 33: --49 ?i? (p+3)h 1 major version number, ascii 34: --31 ?1? (p+4)h 1 minor version number, ascii 35: --31 ?1?
256-mbit j3 (x8/x16) datasheet 57 (p+5)h (p+6)h (p+7)h (p+8)h 4 optional feature and command support (1=yes, 0=no) 36: --0a bits 9?31 are reserved; undefined bits are ?0.? if bit 31 is 37: --00 ?1? then another 31 bit field of optional features follows at 38: --00 the end of the bit-30 field. 39: --00 bit 0 chip erase supported bit 0 = 0 no bit 1 suspend erase supported bit 1 = 1 yes bit 2 suspend program supported bit 2 = 1 yes bit 3 legacy lock/unlock supported bit 3 = 1 (1) yes (1) bit 4 queued erase supported bit 4 = 0 no bit 5 instant individual block locking supported bit 5 = 0 no bit 6 protection bits supported bit 6 = 1 yes bit 7 page-mode read supported bit 7 = 1 yes bit 8 synchronous read supported bit 8 = 0 no (p+9)h 1 supported functions after suspend: read array, status, query other supported operations are: bits 1?7 reserved; undefined bits are ?0? 3a: --01 bit 0 program supported after erase suspend bit 0 = 1 yes (p+a)h (p+b)h 2 block status register mask 3b: --01 bits 2?15 are reserved; undefined bits are ?0? 3c: --00 bit 0 block lock-bit status register active bit 0 = 1 yes bit 1 block lock-down bit status active bit 1 = 0 no (p+c)h 1 v cc logic supply highest performance program/erase voltage bits 0?3 bcd value in 100 mv bits 4?7 bcd value in volts 3d: --33 3.3 v (p+d)h 1 v pp optimum program/erase supply voltage bits 0?3 bcd value in 100 mv bits 4?7 hex value in volts 3e: --00 0.0 v note: 1. future devices may not support the described ?legacy lock/unlock? function. thus bit 3 would have a value of ?0.? table 30. primary vendor-specific extended query (sheet 2 of 2) offset (1) p = 31h length description (optional flash features and commands) add. hex code value
256-mbit j3 (x8/x16) 58 datasheet table 31. protection register information offset (1) p = 31h length description (optional flash features and commands) add. hex code value (p+e)h 1 number of protection register fields in jedec id space. ?00h,? indicates that 256 protection bytes are available 3f: --01 01 (p+f)h (p+10)h (p+11)h (p+12)h 4 protection field 1: protection description this field describes user-available one time programmable (otp) protection register bytes. some are pre-programmed with device-unique serial numbers. others are user- programmable. bits 0-15 point to the protection register lock byte, the section?s first byte. the following bytes are factory pre-programmed and user-programmable. bits 0-7 = lock/bytes jedec-plane physical low address bits 8-15 = lock/bytes jedec-plane physical high address bits 16-23 = ?n? such that 2 n = factory pre-programmed bytes bits 24-31 = ?n? such that 2 n = user-programmable bytes 40: 41: 42: 43: --80 --00 --03 --03 80h 00h 8bytes 8bytes note: 1. the variable p is a pointer which is defined at cfi offset 15h. table 32. burst read information offset (1) p = 31h length description (optional flash features and commands) add. hex code value (p+13)h 1 page mode read capability bits 0?7 = ?n? such that 2 n hex value represents the number of read-page bytes. see offset 28h for device word width to determine page-mode data output width. 00h indicates no read page buffer. 44: --03 8 byte (p+14)h 1 number of synchronous mode read configuration fields that follow. 00h indicates no burst capability. 45: --00 0 (p+15)h reserved for future use 46: note: 1. the variable p is a pointer which is defined at cfi offset 15h.
256-mbit j3 (x8/x16) datasheet 59 appendix b flow charts figure 18. write to buffer flowchart start setup - write 0xe8 - block address check buffer status - perform read operation - read ready status on signal sr7 sr7 = 1? word count - address = block address - data = word count minus 1 (valid range = 0x00 to 0x1f) confirm - write 0xd0 - block address end yes no yes sr7 = 1? no load buffer - fill write buffer up to word count - address = within buffer range - data = user data read status register (sr) full status register check (if desired)
256-mbit j3 (x8/x16) 60 datasheet 0606_07a figure 19. status register flowchart start sr7 = '1' sr2 = '1' sr4 = '1' sr3 = '1' sr1 = '1' yes yes yes no no no no sr6 = '1' yes no sr5 = '1' no no error command sequence yes yes yes error erase failure error program failure - set by wsm - reset by user - see clear status register command - set/reset by wsm sr4 = '1' yes no end command cycle - issue status register command - address = any dev ice address - data = 0x70 erase suspend see suspend/resume flowchart program suspend see suspend/resume flowchart error v pen < v penlk error block locked data cycle - read status register sr[7:0]
256-mbit j3 (x8/x16) datasheet 61 figure 20. byte/word program flowchart start write 40h, address write data and address read status register sr.7 = full status check if desired byte/word program complete read status register data (see above) voltage range error device protect error programming error byte/word program successful sr.3 = sr.1 = sr.4 = full status check procedure bus operation write write standby 1. toggling oe# (low to high to low) updates the status register. this can be done in place of issuing the read status register command. repeat for subsequent programming operations. sr full status check can be done after each program operation, or after a sequence of programming operations. write ffh after the last program operation to place device in read array mode. bus operation standby standby toggling oe# (low to high to low) updates the status register. this can be done in place of issuing the read status register command. repeat for subsequent programming operations. sr.4, sr.3 and sr.1 are only cleared by the clear status register command in cases where multiple locations are programmed before full status is checked. if an error is detected, clear the status register before attempting retry or other error recovery. 0 1 1 0 1 0 1 0 command setup byte/ word program byte/word program comments data = 40h addr = location to be programmed data = data to be programmed addr = location to be programmed check sr.7 1 = wsm ready 0 = wsm busy command comments check sr.3 1 = programming to voltage error detect check sr.4 1 = programming error read (note 1) status register data standby check sr.1 1 = device protect detect rp# = v ih , block lock-bit is set only required for systems implemeting lock-bit configuration.
256-mbit j3 (x8/x16) 62 datasheet 0606_08 figure 21. program suspend/resume flowchart start write b0h read status register sr.7 = sr.2 = programming completed write d0h programming resumed write ffh read array data 1 1 0 0 bus operation command comments write program suspend data = b0h addr = x read status register data addr = x standby check sr.7 1 - wsm ready 0 = wsm busy standby check sr.6 1 = programming suspended 0 = programming completed read read array locations other than that being programmed. write ffh read data array done reading yes no write read array data = ffh addr = x write program resume data = d0h addr = x
256-mbit j3 (x8/x16) datasheet 63 0606_09 figure 22. block erase flowchart start read status register sr.7 = erase flash block(s) complete 0 1 full status check if desired suspend erase issue single block erase command 20h, block address suspend erase loop write confirm d0h block address yes no bus operation command comments write erase block data = 20h addr = block address write (note 1) erase confirm data = d0h addr = x read status register data with the device enabled, oe# low updates sr addr = x standby check sr.7 1 = wsm ready 0 = wsm busy 1. the erase confirm byte must follow erase setup. this device does not support erase queuing. please see application note ap-646 for software erase queuing compatibility. full status check can be done after all erase and write sequences complete. write ffh after the last operation to reset the device to read array mode.
256-mbit j3 (x8/x16) 64 datasheet 0606_10 figure 23. block erase suspend/resume flowchart start write b0h read status register sr.7 = sr.6 = block erase completed read or program? done? wri te d0h block erase resumed write ffh read array data program program loop read array data read no yes 1 1 0 0 bus operation command comments wri te erase suspend data = b0h addr = x read status register data addr = x standby check sr.7 1 - wsm ready 0 = wsm busy standby check sr.6 1 = block erase suspended 0 = block erase completed wri te erase resume data = d0h addr = x
256-mbit j3 (x8/x16) datasheet 65 figure 24. set block lock-bit flowchart start write 60h, block address write 01h, block address read status register sr.7 = full status check if desired set lock-bit complete full status check procedure bus operation write 1 0 command set block lock-bit setup comments data = 60h addr =block address read status register data (see above) voltage range error sr.3 = 1 0 command sequence error sr.4,5 = 1 0 set lock-bit error sr.4 = 1 0 set lock-bit successful bus operation standby command comments check sr.3 1 = programming voltage error detect sr.5, sr.4 and sr.3 are only cleared by the clear status register command, in cases where multiple lock-bits are set before full status is checked. if an error is detected, clear the status register before attempting retry or other error recovery. standby check sr.4, 5 both 1 = command sequence error standby check sr.4 1 = set lock-bit error write set block lock-bit confirm data = 01h addr = block address standby repeat for subsequent lock-bit operations. full status check can be done after each lock-bit set operation or after a sequence of lock-bit set operations. write ffh after the last lock-bit set operation to place device in read array mode. check sr.7 1 = wsm ready 0 = wsm busy read status register data
256-mbit j3 (x8/x16) 66 datasheet figure 25. clear lock-bit flowchart start write 60h write d0h read status register sr.7 = full status check if desired clear block lock-bits complete full status check procedure bus operation write write standby write ffh after the clear lock-bits operation to place device in read array mode. bus operation standby sr.5, sr.4, and sr.3 are only cleared by the clear status register command. if an error is detected, clear the status register before attempting retry or other error recovery. 1 0 command clear block lock-bits setup clear block or lock-bits confirm comments data = 60h addr = x data = d0h addr = x check sr.7 1 = wsm ready 0 = wsm busy command comments check sr.3 1 = programming voltage error detect read status register data (see above) voltage range error sr.3 = 1 0 command sequence error sr.4,5 = 1 0 clear block lock-bits error sr.5 = 1 0 read status register data standby check sr.4, 5 both 1 = command sequence error standby check sr.5 1 = clear block lock-bits error clear block lock-bits successful
256-mbit j3 (x8/x16) datasheet 67 figure 26. protection register programming flowchart start write c0h (protection reg. program setup) write protect. register address/data read status register sr.7 = 1? full status check if desired program complete read status register data (see above) v pen range error protection register programming error attempted program to locked register - aborted program successful sr.3, sr.4 = sr.1, sr.4 = sr.1, sr.4 = full status check procedure bus operation write write standby protection program operations can only be addressed within the protection register address space. addresses outside the defined space will return an error. repeat for subsequent programming operations. sr full status check can be done after each program or after a sequence of program operations. write ffh after the last program operation to reset device to read array mode. bus operation standby standby sr.3 must be cleared, if set during a program attempt, before further attempts are allowed by the write state machine. sr.1, sr.3 and sr.4 are only cleared by the clear staus register command, in cases of multiple protection register program operations before full status is checked. if an error is detected, clear the status register before attempting retry or other error recovery. no yes 1, 1 0,1 1,1 command protection program setup protection program comments data = c0h data = data to program addr = location to program check sr.7 1 = wsm ready 0 = wsm busy command comments sr.1 sr.3 sr.4 0 1 1 v pen low 0 0 1 prot. reg. prog. error 1 0 1 register locked: aborted read status register data toggle ce# or oe# to update status register data standby
256-mbit j3 (x8/x16) 68 datasheet appendix c design considerations c.1 three-line output control the device will often be used in large memory arrays. intel provides five control inputs (ce0, ce1, ce2, oe#, and rp#) to accommodate multiple memory connections. this control provides for: a. lowest possible memory power dissipation. b. complete assurance that data bus contention will not occur. to use these control inputs efficiently, an address decoder should enable the device (see table 13 ) while oe# should be connected to all memory devices and the system?s read# control line. this assures that only selected memory devices have active outputs while de-selected memory devices are in standby mode. rp# should be connected to the system powergood signal to prevent unintended writes during system power transitions. powergood should also toggle during system reset. c.2 sts and block erase, program, and lock-bit configuration polling sts is an open drain output that should be connect ed to vccq by a pull-up resistor to provide a hardware method of detecting block erase, program, and lock-bit configuration completion. it is recommended that a 2.5k resister be used between sts# and vccq. in default mode, it transitions low after block erase, program, or lock-bit configuration commands and returns to high z when the wsm has finished executing the internal algorithm. for alternate configurations of the sts signal, see the configuration command. sts can be connected to an interrupt input of the system cpu or controller. it is active at all times. sts, in default mode, is also high z when the device is in block erase suspend (with programming inactive), program suspend, or in reset/power-down mode. c.3 input signal transitions?reducing overshoots and undershoots when using buffers or transceivers as faster, high-drive devices such as transceivers or buffers drive input signals to flash memory devices, overshoots and undershoots can sometimes cause input signals to exceed flash memory specifications. (see ?dc voltage characteristics? on page 20.) many buffer/transceiver vendors now carry bus-interface devices with internal out put-damping resistors or reduced-drive outputs. internal output-damping resistors diminish the nominal output drive currents, while still leaving sufficient drive capability for most applications. these internal output-damping resistors help reduce unnecessary overshoots and undershoots. tran sceivers or buffers with balanced- or light- drive outputs also reduce overshoots and undershoots by diminishing output-drive currents. when considering a buffer/transceiver interface design to flash, devices with internal output-damping resistors or reduced-drive outputs should be used to minimize overshoots and undershoots. for additional information, please refer to ap-647, 5 volt intel strataflash ? memory design guide (order number: 292205).
256-mbit j3 (x8/x16) datasheet 69 c.4 v cc , v pen , rp# transitions block erase, program, and lock-bit configuration are not guaranteed if v pen or v cc falls outside of the specified operating ranges, or rp# v ih . if rp# transitions to v il during block erase, program, or lock-bit configuration, sts (in default mode) will remain low for a maximum time of t plph + t phrh until the reset operation is complete. then, the operation will abort and the device will enter reset/power-down mode. the aborted operation may leave data partially corrupted after programming, or partially altered after an erase or lock-bit configuration. therefore, block erase and lock-bit configuration commands must be repeated after normal operation is restored. device power-off or rp# = v il clears the status register. the cui latches commands issued by system software and is not altered by v pen , ce 0 , ce 1 , or ce 2 transitions, or wsm actions. its state is read array mode upon power-up, after exit from reset/ power-down mode, or after v cc transitions below v lko . v cc must be kept at or above v pen during v cc transitions. after block erase, program, or lock-bit configuration, even after v pen transitions down to v penlk , the cui must be placed in read array mode via the read array command if subsequent access to the memory array is desired. v pen must be kept at or below v cc during v pen transitions. c.5 power dissipation when designing portable systems, designers must consider battery power consumption not only during device operation, but also for data retention during system idle time. flash memory?s nonvolatility increases usable battery life because data is retained when system power is removed.
256-mbit j3 (x8/x16) 70 datasheet appendix d additional information order number document/tool 298130 intel ? strataflash? memory (j3); 28f256j3, 28f128j3, 28f640j3, 28f320j3 specification update 298136 intel ? persistent storage manager (ipsm) user?s guide software manual 297833 intel ? flash data integrator (fdi) user?s guide software manual 290737 intel strataflash ? synchronous memory (k3/k18); 28f640k3, 28f640k18, 28f128k3, 28f128k18, 28f256k3, 28f256k18 292280 ap-732 3 volt intel strataflash ? memory j3 to k3/k18 migration guide 292237 ap-689 using intel ? persistent storage manager 290606 5 volt intel ? strataflash? memoryi28f320j5 and 28f640j5 datasheet 297859 ap-677 intel ? strataflash? memory technology 292222 ap-664 designing intel ? strataflash? memory into intel ? architecture 292221 ap-663 using the intel ? strataflash? memory write buffer 292218 ap-660 migration guide to 3 volt intel ? strataflash? memory 292204 ap-646 common flash interface (cfi) and command sets 253418 intel ? wireless communications and computing package user?s guide 1. please call the intel literature center at (800) 548-4725 to request intel documentation. international customers should contact their local intel or distribution sales office. 2. visit intel?s world wide web home page at http://www.intel.com for technical documentation and tools. 3. for the most current information on intel strataflash memory, visit our website at http:// developer.intel.com/design/flash/isf.
256-mbit j3 (x8/x16) datasheet 71 appendix e ordering information note: 1. speeds are for either the standard asynchronous read access times or for the first access of a page-mode read sequence. valid combinations p c 2 8 f 2 5 6 j 3 c - 1 2 product line designator for all intel ? flash products access speed (ns) 1 256 mbit = 125 128 mbit = 150, 120 64 mbit = 120, 115 32 mbit = 110 product family j = intel ? strataflash memory, 2 bits-per-cell device density 256 = x8/x16 (256 mbit) 128 = x8/x16 (128 mbit) 640 = x8/x16 (64 mbit) 320 = x8/x16 (32 mbit) voltage (v cc /v pen ) 3 = 3 v/3 v 5 a = intel ? 0.25 micron lithography c = intel? 0.18 micron lithography package e = 56-lead tsop (j3a, 802) te= 56-lead tsop (j3c, 803) js = pb-free 56-tsop rc = 64-ball easy bga ge = 48-ball vfbga pc = 64-ball pb-free easy bga 56-lead tsop 64-ball easy bga 48-ball vf bga e28f320j3a-110 rc28f320j3a-110 ge28f320j3a-110 e28f640j3a-120 rc28f640j3a-120 ge28f320j3c-110 e28f128j3a-150 rc28f128j3a-150 ge28f640j3c-115 te28f320j3c-110 rc28f320j3c-110 ge28f640j3c-120 te28f640j3c-115 rc28f640j3c-115 te28f640j3c-120 rc28f640j3c-120 te28f128j3c-120 rc28f128j3c-120 te28f128j3c-150 rc28f128j3c-150 te28f256j3c-125 rc28f256j3c-125 56-lead pb-free tsop 64-ball pb-free easy bga js28f256j3c125 pc28f256j3c125 js28f128j3c120 pc28f128j3c120 js28f640j3c115 pc28f640j3c115 js28f320j3c110 PC28F320j3c110
256-mbit j3 (x8/x16) 72 datasheet

▲Up To Search▲

Price & Availability of PC28F320

	To Download PC28F320 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .